zap_scan

Comprehensive web application security scanner using OWASP ZAP

SERVERKali Linux MCP Server SOURCEalessandroannini/kali-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/alessandroannini-kali-mcp-server/zap-scan.md

What zap_scan does on Kali Linux MCP Server

AI agents invoke zap_scan to trigger actions in Kali Linux 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 zap_scan is rated High

OWASP ZAP performs active scanning which sends malicious/fuzzing HTTP requests to target web applications, triggering real interactions with external systems. This constitutes execution of security testing operations against potentially unauthorized targets. While it doesn't directly delete data, it can cause unintended side effects on target systems (crashes, data corruption, account lockouts).

From the tool's definition 'Comprehensive web application security scanner using OWASP ZAP' — actively scans web applications, sending attack probes and payloads to target systems

Questions about zap_scan

What does the zap_scan tool do? +

Comprehensive web application security scanner using OWASP ZAP. It is categorised as a Execute tool in the Kali Linux 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 zap_scan? +

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

What risk level is zap_scan? +

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

Can I rate-limit zap_scan? +

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

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

zap_scan is provided by the Kali Linux MCP Server MCP server (alessandroannini/kali-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Kali Linux MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kali Linux MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.