AI agents call estimate_keyspace 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 tool performs mathematical estimation/analysis only. It reads input parameters and returns a calculated keyspace metric to inform attack planning, with no side effects on systems, files, or credentials. While it supports password cracking workflows, the tool itself is purely informational—analogous to a search query or data retrieval operation.
From the tool's definition Tool name 'estimate_keyspace' and description 'Estimate keyspace size for an attack' indicate a computational analysis function that calculates hash search space without modifying data, executing attacks, or triggering external operations.
Documented attack patterns abuse exactly the kind of access estimate_keyspace 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 estimate_keyspace:
{
"version": "1",
"default": "deny",
"tools": {
"estimate_keyspace": {}
}
}estimate_keyspace 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.
Estimate keyspace size for an attack. 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 estimate_keyspace: 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.
estimate_keyspace 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 estimate_keyspace 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 estimate_keyspace. 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.
estimate_keyspace 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.