Start password cracking with John the Ripper. Supports various modes including wordlist, incremental, and single crack.
AI agents invoke john_crack to trigger actions in John The Ripper. 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 code/external operations (John the Ripper binary) with arguments that determine behavior. It is not merely reading data (Read), nor creating/modifying user data reversibly (Write). While it could be destructive in a secondary sense if used against production systems without authorization, the primary capability is executing password attacks.
From the tool's definition Tool starts password cracking with John the Ripper, supporting multiple cracking modes (wordlist, incremental, single crack).
Attacks that exploit this kind of access
Start password cracking with John the Ripper. Supports various modes including wordlist, incremental, and single crack. It is categorised as a Execute tool in the John The Ripper MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the John The Ripper 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 John The Ripper. 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 John The Ripper MCP server (schwarztim/sec-john-the-ripper-mcp). 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 →