Manage Hardhat contract deployment and interaction. OPERATIONS: - deploy: Execute deployment script on target network - deploy_ignition: Deploy using Hardhat Ignition (declarative) - verify: Get contract verification metadata for HashScan - call: Call read-only contract function (FREE) - execute:...
AI agents invoke hardhat_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.
The tool spans multiple severity levels: 'deploy' and 'execute' are Execute-category operations that trigger blockchain transactions with real-world effects; 'call' is Read-only and safe. The 'execute' operation for state-changing transactions and deployment operations are the most severe.
From the tool's definition Tool explicitly supports 'deploy' (execute deployment script), 'deploy_ignition' (declarative deployment), and 'execute' (execute state-changing contract transaction).
Attacks that exploit this kind of access
Manage Hardhat contract deployment and interaction. OPERATIONS: - deploy: Execute deployment script on target network - deploy_ignition: Deploy using Hardhat Ignition (declarative) - verify: Get contract verification metadata for HashScan - call: Call read-only contract function (FREE) - execute: Execute state-changing contract transaction AUTO-RESOLUTION: Deployment automatically uses MCP operator account credentials. No need to set TESTNET_PRIVATE_KEY manually. USE FOR: Contract deployment, verification, and interaction. 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_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_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_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_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_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 →