Check the status of a cracking session
AI agents call john_status 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 the current state of a password cracking session. It performs a passive read operation with no side effects, no code execution, no data modification, and no destructive actions. While the server overall is used for security auditing (which involves executing John the Ripper), this specific tool merely queries session status.
From the tool's definition Tool name 'john_status' and description 'Check the status of a cracking session' indicate a query operation that retrieves information about an ongoing process without modifying, executing new operations, or deleting data.
Attacks that exploit this kind of access
Check the status of a cracking session. 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_status: 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_status 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_status 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_status. 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_status 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 →