AI agents call mirror_get_contract_results 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 historical data about contract execution from the Hedera mirror node. It performs a query-only operation to fetch and display past transaction results, gas consumption metrics, and associated error logs. There are no side effects, no data modification, no code execution, and no financial transactions involved. This is a straightforward Read operation.
From the tool's definition Tool description states 'Get contract execution history' and 'Returns transaction results, gas used, and error messages' — pure retrieval operations with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get contract execution history. Returns transaction results, gas used, and error messages. 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_contract_results: 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_contract_results 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_contract_results 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_contract_results. 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_contract_results 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 →