AI agents call get_hash_categories 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.
This is a straightforward read operation that retrieves reference information about available hash categories supported by the hashcat server. It has no side effects and does not modify, delete, or execute any operations. The blast radius of misuse is minimal—an AI agent accessing this data cannot cause harm beyond learning what hash types are supported.
From the tool's definition Tool name 'get_hash_categories' and description 'Get all available hash categories' indicate a retrieval operation that lists or queries static metadata about supported hash types. No data creation, modification, deletion, or external command execution occurs.
Documented attack patterns abuse exactly the kind of access get_hash_categories gives an agent:
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_hash_categories:
{
"version": "1",
"default": "deny",
"tools": {
"get_hash_categories": {}
}
} get_hash_categories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all available hash categories. It is categorised as a Read tool in the Hashcat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hashcat MCP Server MCP server in PolicyLayer and add a rule for get_hash_categories: 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.
get_hash_categories 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 get_hash_categories 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 get_hash_categories. 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.
get_hash_categories 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.
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.