cancel_scan
AI agents call cancel_scan to permanently remove resources in Burp Suite MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a scan is generally an irreversible action — once stopped, the scan progress and collected data may be lost and cannot be resumed. Given the sibling tools (active scans, scan progress, etc.), this tool almost certainly terminates a running security scan. The empty description lowers confidence, but the name strongly implies a destructive, non-undoable operation.
From the tool's definition Tool name 'cancel_scan' implies irreversible termination of an active scan; description is empty providing no additional context.
Attacks that exploit this kind of access
cancel_scan. It is categorised as a Destructive tool in the Burp Suite MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Burp Suite MCP Server MCP server in PolicyLayer and add a rule for cancel_scan: 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.
cancel_scan is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_scan 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 cancel_scan. 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.
cancel_scan 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 →