AI agents call mirror_get_account_tokens 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 displays data about token holdings and statuses without side effects. It is a read-only query against the Hedera blockchain state. The low severity reflects minimal risk if misused by an agent—reading account token information cannot damage systems or cause financial loss.
From the tool's definition Tool name and description indicate a query-only operation: 'Get all token relationships for an account' with return values of 'token associations, balances, freeze/KYC status'. No modification, creation, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
Get all token relationships for an account. Returns token associations, balances, freeze/KYC status. 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_get_account_tokens: 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_get_account_tokens 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_get_account_tokens 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_get_account_tokens. 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_get_account_tokens 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 →