AI agents call hardhat_call_contract 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 data from smart contracts without executing state-changing operations. It is classified as Read because it queries contract state through view or pure functions, which are guaranteed by Solidity language semantics to have no side effects. The low severity reflects that misuse would only expose existing data, not modify blockchain state or assets.
From the tool's definition Tool is described as 'Call read-only contract function (view/pure). No gas cost.' The 'view/pure' keyword restriction and explicit 'read-only' designation confirm this performs only data retrieval with no state modifications.
Attacks that exploit this kind of access
Call read-only contract function (view/pure). No gas cost. 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 hardhat_call_contract: 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.
hardhat_call_contract 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 hardhat_call_contract 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 hardhat_call_contract. 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.
hardhat_call_contract 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 →