# zap_scan

Comprehensive web application security scanner using OWASP ZAP

Agent View of the PolicyLayer registry record for `zap_scan`. HTML page: https://policylayer.com/tools/alessandroannini-kali-mcp-server/zap-scan

## Facts

- Tool: `zap_scan`
- Server: Kali Linux MCP Server (`alessandroannini/kali-mcp-server`) — https://policylayer.com/tools/alessandroannini-kali-mcp-server.md
- Homepage: https://github.com/AlessandroAnnini/kali-mcp-server
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "zap_scan",
    "arguments": {}
  }
}
```

## 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 own definition: "'Comprehensive web application security scanner using OWASP ZAP' — actively scans web applications, sending attack probes and payloads to target systems"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kali Linux MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "zap_scan": {
      "limits": [
        {
          "counter": "zap_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Kali Linux MCP Server (13)

- `dirb_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/dirb-scan.md
- `jwt_security_test` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/jwt-security-test.md
- `nikto_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/nikto-scan.md
- `nmap_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/nmap-scan.md
- `nuclei_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/nuclei-scan.md
- `retirejs_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/retirejs-scan.md
- `sqlmap_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/sqlmap-scan.md
- `testssl_scan` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/testssl-scan.md
- `vpn_connect` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/vpn-connect.md
- `vpn_disconnect` — Execute — https://policylayer.com/tools/alessandroannini-kali-mcp-server/vpn-disconnect.md
- `jwt_decode` — Read — https://policylayer.com/tools/alessandroannini-kali-mcp-server/jwt-decode.md
- `security_headers_check` — Read — https://policylayer.com/tools/alessandroannini-kali-mcp-server/security-headers-check.md
- `vpn_status` — Read — https://policylayer.com/tools/alessandroannini-kali-mcp-server/vpn-status.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=alessandroannini-kali-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/alessandroannini-kali-mcp-server