get_scan_summary
AI agents call get_scan_summary to retrieve information from Burp Suite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries scan summary information from Burp Suite without modifying, executing, or deleting anything. It fits the Read category pattern of the server (fetch/get operations). However, the empty description and potential for information disclosure (scan summaries may reveal discovered vulnerabilities) elevates severity from low to medium.
From the tool's definition Tool name 'get_scan_summary' indicates retrieval of scan summary data. Server description shows tools like 'check_security_scan_progress' and 'list_active_scans' are also Read operations. Tool description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
get_scan_summary. It is categorised as a Read tool in the Burp Suite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Burp Suite MCP Server MCP server in PolicyLayer and add a rule for get_scan_summary: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Burp Suite MCP Server. Nothing to install.
get_scan_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_scan_summary rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for get_scan_summary. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
get_scan_summary is provided by the Burp Suite MCP Server MCP server (jayluxferro/burp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →