AI agents call verification_status 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 and retrieves existing verification status information for contracts. It performs no mutations, deletions, financial transactions, or code execution. The description emphasizes checking/viewing status without re-verifying, confirming its read-only nature. On the Hedera blockchain context, checking contract verification status is a standard informational query with no side effects.
From the tool's definition Tool description explicitly states "Check verification status" and "Returns verification status and library mappings" — retrieves data about contract verification status on HashScan without modifying anything.
Attacks that exploit this kind of access
Check verification status for one or more contracts on HashScan without re-verifying. Returns verification status and library mappings. 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 verification_status: 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.
verification_status 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 verification_status 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 verification_status. 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.
verification_status 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 →