reaver_attack · Kali MCP: Risk & Policy

WHAT IT DOES

What reaver_attack does on Kali

AI agents invoke reaver_attack to trigger actions in Kali. 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 reaver_attack needs a policy

Reaver is a specific offensive security tool that performs brute-force attacks against WPS-enabled wireless access points to recover WPA/WPA2 passphrases. It actively attacks external systems, making it Execute at minimum. The blast radius is critical as it can compromise wireless network credentials of third-party networks.

From the tool's definition Tool name 'reaver_attack' on a Kali Linux penetration testing server supporting 'password attacks'. Reaver is a well-known WPS (Wi-Fi Protected Setup) brute-force attack tool used to crack WPA/WPA2 passwords.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reaver_attack Rate-limited

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

FAQ

Questions about reaver_attack

What does the reaver_attack tool do? +

reaver_attack. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reaver_attack? +

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

What risk level is reaver_attack? +

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

Can I rate-limit reaver_attack? +

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

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

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