scan_urls_for_vulnerabilities · Burp Suite MCP Server MCP

WHAT IT DOES

What scan_urls_for_vulnerabilities does on Burp Suite MCP Server

AI agents invoke scan_urls_for_vulnerabilities to trigger actions in Burp Suite MCP Server. 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.

WHY IT NEEDS A POLICY

Why scan_urls_for_vulnerabilities needs a policy

The tool triggers active vulnerability scans against URLs using Burp Suite, which involves sending probes, payloads, and requests to external targets. This is an Execute-category action as it initiates external operations whose effects depend on the URLs provided. The description is empty, but the name and server context strongly imply active scanning.

From the tool's definition Tool name 'scan_urls_for_vulnerabilities' combined with server context: 'enabling users to trigger vulnerability scans' and 'Exposes Burp Suite's REST API'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scan_urls_for_vulnerabilities Rate-limited

scan_urls_for_vulnerabilities stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scan_urls_for_vulnerabilities": {
      "limits": [
        {
          "counter": "scan_urls_for_vulnerabilities_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Burp Suite MCP Server, so you can run agents against it safely.

FAQ

Questions about scan_urls_for_vulnerabilities

What does the scan_urls_for_vulnerabilities tool do? +

scan_urls_for_vulnerabilities. It is categorised as a Execute tool in the Burp Suite MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scan_urls_for_vulnerabilities? +

Register the Burp Suite MCP Server MCP server in PolicyLayer and add a rule for scan_urls_for_vulnerabilities: 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.

What risk level is scan_urls_for_vulnerabilities? +

scan_urls_for_vulnerabilities is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scan_urls_for_vulnerabilities? +

Yes. Add a rate_limit block to the scan_urls_for_vulnerabilities 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.

How do I block scan_urls_for_vulnerabilities completely? +

Set action: deny in the PolicyLayer policy for scan_urls_for_vulnerabilities. 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.

What MCP server provides scan_urls_for_vulnerabilities? +

scan_urls_for_vulnerabilities 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.