Show cracked passwords from a hash file or pot file
AI agents call john_show to retrieve information from John The Ripper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays previously cracked passwords stored in pot files or hash files. It performs no modifications, deletions, code execution, or financial operations. While the context involves password cracking (a sensitive security domain), the tool itself is a passive query that reads and displays data without side effects.
From the tool's definition Tool name 'john_show' and description 'Show cracked passwords from a hash file or pot file' indicate data retrieval only. The verb 'show' combined with 'from' (not 'to' or 'modify') confirms read-only querying of existing cracked password results.
Attacks that exploit this kind of access
Show cracked passwords from a hash file or pot file. It is categorised as a Read tool in the John The Ripper MCP Server, which means it retrieves data without modifying state.
Register the John The Ripper MCP server in PolicyLayer and add a rule for john_show: 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_show is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the john_show 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_show. 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_show 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 →