john_crack
AI agents invoke john_crack to trigger actions in MCP Kali 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.
John the Ripper is a well-known password cracking tool. On a Kali Linux MCP server designed for penetration testing, 'john_crack' almost certainly executes password cracking operations. While the description is empty (lowering confidence slightly), the naming convention and server context make this clear.
From the tool's definition Tool name 'john_crack' on a Kali Linux penetration testing server with sibling tools including hydra_attack, metasploit_run, sqlmap_scan — strongly implies John the Ripper password cracking execution.
Attacks that exploit this kind of access
john_crack. It is categorised as a Execute tool in the MCP Kali Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Server MCP server in PolicyLayer and add a rule for john_crack: 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 MCP Kali Server. Nothing to install.
john_crack 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 john_crack 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 john_crack. 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.
john_crack is provided by the MCP Kali Server MCP server (wh0am123/mcp-kali-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.