AI agents call mirror_get_schedule 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 information about scheduled transactions on the Hedera blockchain. The verb 'Get' and the focus on returning details (signatories, expiration, execution status) confirm it is a retrieval operation with no side effects. It does not create, modify, delete, or execute transactions—it only reads their state.
From the tool's definition Tool name 'mirror_get_schedule' and description 'Get scheduled transaction details. Returns signatories, expiration, and execution status.' indicate a read-only query operation that retrieves existing blockchain data without modification or execution.
Attacks that exploit this kind of access
Get scheduled transaction details. Returns signatories, expiration, and execution 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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 →