hardhat_deploy_ignition · HashPilot MCP: Risk & Policy

WHAT IT DOES

What hardhat_deploy_ignition does on HashPilot

AI agents invoke hardhat_deploy_ignition 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.

WHY IT NEEDS A POLICY

Why hardhat_deploy_ignition needs a policy

Deploying smart contracts via Hardhat Ignition is an irreversible execution action that triggers blockchain transactions, modifies chain state, and creates persistent on-chain artifacts. While not immediately destructive (contracts can theoretically be replaced), the effects are permanent and user/argument-dependent, making this an Execute-category tool.

From the tool's definition Tool name includes 'deploy' and description states 'Deploy contracts using Hardhat Ignition'; deployment executes code on the blockchain whose effects depend on contract arguments and state changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hardhat_deploy_ignition Rate-limited

hardhat_deploy_ignition stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hardhat_deploy_ignition": {
      "limits": [
        {
          "counter": "hardhat_deploy_ignition_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HashPilot, so you can run agents against it safely.

FAQ

Questions about hardhat_deploy_ignition

What does the hardhat_deploy_ignition tool do? +

Deploy contracts using Hardhat Ignition (modern declarative deployment). 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.

How do I enforce a policy on hardhat_deploy_ignition? +

Register the HashPilot MCP server in PolicyLayer and add a rule for hardhat_deploy_ignition: 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.

What risk level is hardhat_deploy_ignition? +

hardhat_deploy_ignition is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hardhat_deploy_ignition? +

Yes. Add a rate_limit block to the hardhat_deploy_ignition 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.

How do I block hardhat_deploy_ignition completely? +

Set action: deny in the PolicyLayer policy for hardhat_deploy_ignition. 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.

What MCP server provides hardhat_deploy_ignition? +

hardhat_deploy_ignition 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.