start_complete_scan · ZAP MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_complete_scan does on ZAP MCP Server

AI agents invoke start_complete_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_complete_scan needs a policy

This tool triggers the execution of an automated security scanner that will interact with web applications and systems under test, including active scanning which can modify target behavior and state. While the purpose is security testing (legitimate use), the tool's capability to execute external operations on specified targets matches the Execute category.

From the tool's definition The tool 'start_complete_scan' initiates automated security scanning operations that execute external security testing tools (OWASP ZAP) with real-time side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_complete_scan Rate-limited

start_complete_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_complete_scan": {
      "limits": [
        {
          "counter": "start_complete_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_complete_scan

What does the start_complete_scan tool do? +

Start a complete security scan including AJAX, spider, and active scanning (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_complete_scan? +

Register the ZAP MCP Server MCP server in PolicyLayer and add a rule for start_complete_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_complete_scan? +

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

Can I rate-limit start_complete_scan? +

Yes. Add a rate_limit block to the start_complete_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_complete_scan completely? +

Set action: deny in the PolicyLayer policy for start_complete_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_complete_scan? +

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