AI agents call mirror_query_topic_messages 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 queries existing blockchain data (topic messages, sequences, timestamps, hashes) from a public mirror node without side effects. It does not create, modify, delete, or execute operations.
From the tool's definition Tool description states it 'Query[s] HCS topic messages' and 'Returns message content, sequence numbers, timestamps, and hashes.' The verb 'query' combined with 'returns' indicates read-only retrieval of data from the Hedera Mirror Node with no modifications,…
Attacks that exploit this kind of access
Query HCS topic messages from Hedera Mirror Node. Returns message content, sequence numbers, timestamps, and hashes. No API key required. 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_query_topic_messages: 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_query_topic_messages 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_query_topic_messages 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_query_topic_messages. 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_query_topic_messages 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 →