How to Generate a Security Report with Copilot
Generate a Security Report with Copilot and ToolRouter. Run a comprehensive security assessment across a domain or IP and get a structured report covering all threat vectors.
Tool
Use Copilot with Security Scanner to generate `security_report` output and embed the findings directly into your codebase documentation, infrastructure runbook, or security configuration files. Copilot works best when the report feeds a structured workspace artifact rather than a standalone document.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
Steps
Once connected (see setup above), use the Security Scanner tool:
- Identify the domain or IP to assess within your infrastructure runbook or config file.
- Ask Copilot to run `security_report` via `security-scanner` for the target.
- Have Copilot return the findings as structured JSON matching your security schema.
- Append the security findings to the relevant infrastructure documentation or config entry in the repo.
Example Prompt
Try this with Copilot using the Security Scanner tool
Use security-scanner to generate a security report for vendorname.com. Return the findings as JSON with fields: target, overall_risk_score, threat_categories, top_findings, and recommended_action. I'll embed this in our vendor security record in the infrastructure runbook.
Tips
- Return report findings as structured JSON from the start so they slot into your schema without reformatting.
- Include a `last_checked` timestamp in the output so the infrastructure runbook shows how fresh the assessment is.
- Re-run and diff against the previous run quarterly to track changes in vendor security posture.