Network hashrate + difficulty history.
AI agents call hashrate to retrieve information from Mcp Mempool Space without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available blockchain statistics (hashrate and difficulty history). It performs a read-only operation with no capability to modify, delete, or execute code. The data returned is informational and historical in nature, typical of a block explorer. No financial transactions, destructive operations, or code execution are possible.
From the tool's definition Tool name 'hashrate' and description 'Network hashrate + difficulty history' indicate data retrieval only. Returns historical statistics about Bitcoin network hashrate and difficulty with no mutations, deletions, or side effects.
Attacks that exploit this kind of access
Network hashrate + difficulty history. It is categorised as a Read tool in the Mcp Mempool Space MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mempool Space MCP server in PolicyLayer and add a rule for hashrate: 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 Mcp Mempool Space. Nothing to install.
hashrate 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 hashrate 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 hashrate. 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.
hashrate is provided by the Mcp Mempool Space MCP server (pipeworx-io/mcp-mempool-space). 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 →