List all active and saved John the Ripper sessions
AI agents call john_sessions 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 information about existing John the Ripper sessions without creating, modifying, executing, or deleting anything. It is a read-only operation that queries session metadata. While the broader server enables password cracking (which could raise concerns), this specific tool merely lists sessions—comparable to a 'get' or 'list' operation.
From the tool's definition Tool name 'john_sessions' with description 'List all active and saved John the Ripper sessions' performs query/retrieval of session state with no modification or execution capability.
Attacks that exploit this kind of access
List all active and saved John the Ripper sessions. 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_sessions: 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_sessions 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_sessions 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_sessions. 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_sessions 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 →