AI agents invoke crunch_generate 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.
Crunch is a wordlist/password generator tool commonly used in Kali Linux for password attack preparation. The tool likely generates wordlists used in brute-force or dictionary attacks. The description is empty, lowering confidence, but the server context (penetration testing, password attacks) and the tool name strongly suggest it generates password lists.
From the tool's definition Tool name: crunch_generate; server description mentions 'password attacks' among 90+ tools on a Kali Linux penetration testing server.
Attacks that exploit this kind of access
crunch_generate. 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.
Register the Kali MCP server in PolicyLayer and add a rule for crunch_generate: 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.
crunch_generate 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 crunch_generate 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 crunch_generate. 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.
crunch_generate 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.
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 →