AI agents call mirror_list_balances 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 retrieves and filters existing blockchain balance data without creating, modifying, deleting, or executing any transactions. It has no side effects on the blockchain state. While it could expose financial information (account balances), the tool itself performs only read operations, making it a Read category risk.
From the tool's definition Tool description states 'List network balance snapshots' and 'historical balance queries', which are retrieval operations with no modification or execution. The verb 'list' and 'query' indicate read-only access to balance data.
Attacks that exploit this kind of access
List network balance snapshots. Filter by account or timestamp for historical balance queries. 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_balances: 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_balances 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_balances 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_balances. 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_balances 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 →