start_active_scan · ZAP MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_active_scan does on ZAP MCP Server

AI agents invoke start_active_scan to trigger actions in ZAP 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 start_active_scan needs a policy

This tool triggers execution of active security scanning operations on external targets. Active scans generate network traffic, probe for vulnerabilities, and interact with target systems - these are code/command execution equivalents in security context. While the purpose is defensive (vulnerability testing), the tool's ability to execute operations against arbitrary URLs makes it Execute category.

From the tool's definition Tool performs 'Start an active security scan on a target URL' - actively executes security testing operations against a specified target, which is an external operation with side effects that depend on the arguments provided (the target URL and scan…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_active_scan Rate-limited

start_active_scan 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": {
    "start_active_scan": {
      "limits": [
        {
          "counter": "start_active_scan_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 ZAP MCP Server, so you can run agents against it safely.

FAQ

Questions about start_active_scan

What does the start_active_scan tool do? +

Start an active security scan on a target URL (asynchronous). It is categorised as a Execute tool in the ZAP 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 start_active_scan? +

Register the ZAP MCP Server MCP server in PolicyLayer and add a rule for start_active_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 ZAP MCP Server. Nothing to install.

What risk level is start_active_scan? +

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

Can I rate-limit start_active_scan? +

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

How do I block start_active_scan completely? +

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

What MCP server provides start_active_scan? +

start_active_scan is provided by the ZAP MCP Server MCP server (lisberndt/zap-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.