Manage Hardhat project lifecycle operations. OPERATIONS: - init: Initialize new Hardhat project with Hedera configuration - compile: Compile Solidity contracts (with force option) - test: Run Mocha/Chai tests with filtering - clean: Clean artifacts and cache - flatten: Flatten contracts for verif...
AI agents invoke hardhat_project 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.
While some operations like 'list_tasks', 'get_accounts', and 'config_network' are Read operations, the tool's primary purpose centers on code compilation, testing, and custom task execution—all of which run code whose effects depend on arguments and project contents. The 'run_task' operation is explicitly Execute, and 'compile' generates executable bytecode.
From the tool's definition The tool provides multiple execution capabilities: 'init' (initialize projects), 'compile' (compile code), 'test' (run test suites), 'run_task' (execute custom Hardhat tasks), and 'get_artifacts' (retrieve compiled bytecode).
Attacks that exploit this kind of access
Manage Hardhat project lifecycle operations. OPERATIONS: - init: Initialize new Hardhat project with Hedera configuration - compile: Compile Solidity contracts (with force option) - test: Run Mocha/Chai tests with filtering - clean: Clean artifacts and cache - flatten: Flatten contracts for verification - get_artifacts: Retrieve compiled ABI and bytecode - get_accounts: List available accounts with balances - config_network: Generate Hedera network config snippet - run_task: Execute custom Hardhat task - list_tasks: List all available tasks USE FOR: Project setup, compilation, testing, and configuration management. 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_project: 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_project 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_project 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_project. 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_project 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 →