reaver_attack

What reaver_attack does on Kali Security MCP

AI agents invoke reaver_attack to trigger actions in Kali Security MCP. 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 reaver_attack is rated High

This tool executes an external security/attack operation (WPS PIN brute-force attacks) whose effects depend on the target network specified as an argument. It performs active exploitation rather than passive reconnaissance or data modification. While highly destructive in intent (breaking into wireless networks), the actual tool itself executes an attack workflow whose success/failure depends on external factors.

From the tool's definition Tool name 'reaver_attack' combined with description 'Execute Reaver for WPS PIN attacks' indicates active execution of a penetration testing attack tool. Reaver is a real WPS (WiFi Protected Setup) brute-force tool used to crack wireless network credentials.

The rule that runs reaver_attack safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kali Security MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reaver_attack, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reaver_attack": {
      "limits": [
        {
          "counter": "reaver_attack_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about reaver_attack