aircrack_attack
AI agents invoke aircrack_attack 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.
Aircrack-ng is a well-known WiFi network security tool used to crack WEP/WPA/WPA2 keys. The 'attack' suffix and server context (Kali Linux, password cracking, exploitation frameworks) strongly indicate this tool performs active wireless credential attacks. This is Execute/critical as it actively attacks external network infrastructure.
From the tool's definition Tool name 'aircrack_attack' combined with server context exposing 'password cracking' and 'penetration testing' tools on a Kali Linux platform; sibling tools include 'bully_attack' (WiFi WPS attack) confirming offensive wireless attack capability.
Attacks that exploit this kind of access
aircrack_attack. 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.
Register the Kali Linux MCP Server MCP server in PolicyLayer and add a rule for aircrack_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 Linux MCP Server. Nothing to install.
aircrack_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 aircrack_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 aircrack_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.
aircrack_attack is provided by the Kali Linux MCP Server MCP server (ofryma/custom-mcp-library). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →