Burp Suite Professional automated scanner. Requires Burp Suite Pro license and REST API.
AI agents invoke burpsuite_scan to trigger actions in MCP Kali Pentest. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Burp Suite's automated scanner actively probes web applications by sending crafted HTTP requests, fuzzing parameters, and testing for vulnerabilities. This constitutes executing external operations against target systems. The blast radius is high because an AI agent could direct scans at unauthorized targets or trigger intrusive tests that disrupt production systems.
From the tool's definition Burp Suite Professional automated scanner - runs automated web application security scanning against targets via REST API
Attacks that exploit this kind of access
Burp Suite Professional automated scanner. Requires Burp Suite Pro license and REST API. It is categorised as a Execute tool in the MCP Kali Pentest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for burpsuite_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 MCP Kali Pentest. Nothing to install.
burpsuite_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the burpsuite_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 burpsuite_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.
burpsuite_scan is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). 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 →