AI agents invoke hardhat_execute_contract to trigger actions in HashPilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary contract functions on the Hedera blockchain with financial and state implications. While 'Execute' is the primary category, the tool commits blockchain transactions that cost gas and alter contract state irreversibly.
From the tool's definition Tool description explicitly states 'Execute state-changing contract function' and 'sends transaction' on blockchain. The word 'Execute' combined with state-changing operations and gas requirements indicates code execution with external effects.
Attacks that exploit this kind of access
Execute state-changing contract function. Requires gas and sends transaction. It is categorised as a Execute tool in the HashPilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HashPilot MCP server in PolicyLayer and add a rule for hardhat_execute_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_execute_contract is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hardhat_execute_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_execute_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_execute_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 →