Block share by mining pool.
AI agents call mining_pools 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 retrieves and displays information about mining pool block shares—a read-only query operation on public blockchain data. It has no side effects, cannot modify data, execute code, delete information, or affect financial transactions. The minimal blast radius if misused (e.g., gathering intelligence on mining distribution) does not escalate beyond information disclosure.
From the tool's definition Tool name 'mining_pools' with description 'Block share by mining pool' indicates data retrieval of mining pool statistics. Server description confirms it provides 'tools to query fees, mempool stats, blocks, transactions, addresses, hashrate, and mining pools.
Attacks that exploit this kind of access
Block share by mining pool. 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 mining_pools: 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.
mining_pools 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 mining_pools 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 mining_pools. 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.
mining_pools 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 →