bully_attack
AI agents invoke bully_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.
Bully is a WPS brute-force attack tool for cracking WiFi Protected Setup PINs to gain unauthorized access to wireless networks. The 'attack' suffix and context of sibling tools like aircrack_attack confirm this is an offensive security/exploitation tool. Even with an empty description, the tool name and server context strongly indicate it executes active attacks against wireless infrastructure.
From the tool's definition Tool name 'bully_attack' on a server exposing penetration testing tools including 'password cracking' and 'exploitation frameworks'; sibling tools include 'aircrack_attack' suggesting wireless attack tools
Attacks that exploit this kind of access
bully_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 bully_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.
bully_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 bully_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 bully_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.
bully_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 →