AI agents call mirror_list_blocks to retrieve information from HashPilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries blockchain data and returns immutable historical information about blocks. It performs a read operation against a public ledger without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could only enumerate blocks, which is already public information on a blockchain.
From the tool's definition Tool description states it 'List Hedera blocks (record files). Returns block hashes, numbers, timestamps, and transaction counts.' The verb 'List' and the read-only outputs (hashes, numbers, timestamps, counts) indicate pure data retrieval with no side…
Attacks that exploit this kind of access
List Hedera blocks (record files). Returns block hashes, numbers, timestamps, and transaction counts. It is categorised as a Read tool in the HashPilot MCP Server, which means it retrieves data without modifying state.
Register the HashPilot MCP server in PolicyLayer and add a rule for mirror_list_blocks: 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 HashPilot. Nothing to install.
mirror_list_blocks 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 mirror_list_blocks 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 mirror_list_blocks. 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.
mirror_list_blocks is provided by the HashPilot MCP server (justmert/hashpilot). 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 →