Low Risk

get_session_status

Get real-time status of hashcat session

How to control get_session_status ↓

What get_session_status does on Hashcat MCP Server

AI agents call get_session_status to retrieve information from Hashcat MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_session_status needs a policy

This tool retrieves status information about an existing hashcat session. It performs monitoring/observation only, matching the 'Read' category definition (retrieves or queries data; no side effects). While hashcat itself is used for password cracking, this specific tool merely queries the state of an ongoing session rather than initiating attacks, modifying data, or executing new operations.

From the tool's definition Tool name 'get_session_status' and description 'Get real-time status of hashcat session' indicate a query/retrieval operation with no data modification or side effects.

Documented attack patterns abuse exactly the kind of access get_session_status gives an agent:

How to control get_session_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Hashcat MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_session_status": {}
  }
}

get_session_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Hashcat MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_session_status

What does the get_session_status tool do? +

Get real-time status of hashcat session. It is categorised as a Read tool in the Hashcat MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_status? +

Register the Hashcat MCP Server MCP server in PolicyLayer and add a rule for get_session_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 Hashcat MCP Server. Nothing to install.

What risk level is get_session_status? +

get_session_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_session_status? +

Yes. Add a rate_limit block to the get_session_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.

How do I block get_session_status completely? +

Set action: deny in the PolicyLayer policy for get_session_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.

What MCP server provides get_session_status? +

get_session_status is provided by the Hashcat MCP Server MCP server (mordavid/hashcat-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hashcat MCP Server tool call.

Start from Hashcat MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

23 Hashcat MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.