hardhat_deploy · HashPilot MCP: Risk & Policy

WHAT IT DOES

What hardhat_deploy does on HashPilot

AI agents invoke hardhat_deploy 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 needs a policy

This tool executes code (a deployment script) that deploys smart contracts to a live blockchain network. While not destructive in isolation, deployment is an irreversible operation that commits code to production and has financial implications (gas/transaction fees). The Execute category is most appropriate because the tool's primary function is to trigger external operations whose effects depend on script arguments.

From the tool's definition Tool name 'hardhat_deploy' and description 'Execute deployment script to deploy contracts to Hedera networks' explicitly indicate executing deployment scripts that trigger external blockchain operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hardhat_deploy Rate-limited

hardhat_deploy 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": {
      "limits": [
        {
          "counter": "hardhat_deploy_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

What does the hardhat_deploy tool do? +

Execute deployment script to deploy contracts to Hedera networks. 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? +

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

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

Can I rate-limit hardhat_deploy? +

Yes. Add a rate_limit block to the hardhat_deploy 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 completely? +

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

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