owasp_zap_scan · MCP Kali Pentest MCP: Risk & Policy

WHAT IT DOES

What owasp_zap_scan does on MCP Kali Pentest

AI agents invoke owasp_zap_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.

WHY IT NEEDS A POLICY

Why owasp_zap_scan needs a policy

OWASP ZAP's active scan mode actively probes and attacks a target web application with malicious payloads to discover vulnerabilities. This constitutes executing external operations against a target system. While it doesn't irreversibly delete data, it can cause disruption, trigger WAF bans, generate logs on target systems, and potentially exploit vulnerabilities in unintended ways.

From the tool's definition 'automated security scanner' that 'performs active and passive scanning of web applications' — active scanning sends attack payloads to target applications

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

owasp_zap_scan Rate-limited

owasp_zap_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": {
    "owasp_zap_scan": {
      "limits": [
        {
          "counter": "owasp_zap_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 MCP Kali Pentest, so you can run agents against it safely.

FAQ

Questions about owasp_zap_scan

What does the owasp_zap_scan tool do? +

OWASP ZAP automated security scanner. Performs active and passive scanning of web applications. 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.

How do I enforce a policy on owasp_zap_scan? +

Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for owasp_zap_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.

What risk level is owasp_zap_scan? +

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

Can I rate-limit owasp_zap_scan? +

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

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

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