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.
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.
Documented attack patterns abuse exactly the kind of access reaver_attack gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali Security MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for reaver_attack:
{
"version": "1",
"default": "deny",
"tools": {
"reaver_attack": {
"limits": [
{
"counter": "reaver_attack_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Execute Reaver for WPS PIN attacks. It is categorised as a Execute tool in the Kali Security MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Security 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 Security MCP. Nothing to install.
reaver_attack is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
reaver_attack is provided by the Kali Security MCP server (seac-25/kali-security-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 249 Kali Security MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
249 Kali Security MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.