hardhat_compile · HashPilot MCP: Risk & Policy

WHAT IT DOES

What hardhat_compile does on HashPilot

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

Solidity compilation generates bytecode artifacts that will be executed on the Hedera blockchain. This goes beyond simple read/write data operations—it transforms source code into executable form. Although compilation is not inherently destructive and doesn't move funds directly, it is an Execute operation because it produces executable code artifacts whose on-chain effects depend on the input contracts.

From the tool's definition Tool 'Compile all Solidity contracts' generates executable artifacts (bytecode). Bytecode compilation is code generation that produces machine-executable output; while compilation itself is typically deterministic, the generated bytecode can be deployed and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hardhat_compile Rate-limited

hardhat_compile 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_compile": {
      "limits": [
        {
          "counter": "hardhat_compile_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_compile

What does the hardhat_compile tool do? +

Compile all Solidity contracts in the project. Generates artifacts (ABI, bytecode) and build-info files for verification. 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_compile? +

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

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

Can I rate-limit hardhat_compile? +

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

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

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