foundry_create · HashPilot MCP: Risk & Policy

WHAT IT DOES

What foundry_create does on HashPilot

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

Deploying a smart contract to a blockchain is an irreversible on-chain operation that executes code and consumes gas/HBAR. While not purely destructive (it creates rather than deletes), it triggers an external blockchain operation with permanent effects. The blast radius is high because a malicious or buggy contract deployed by an AI agent could be exploited, drain funds, or cause harm on the Hedera network.

From the tool's definition Deploy a single contract to Hedera network using forge create

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

foundry_create Rate-limited

foundry_create 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": {
    "foundry_create": {
      "limits": [
        {
          "counter": "foundry_create_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 foundry_create

What does the foundry_create tool do? +

Deploy a single contract to Hedera network using forge create. For complex multi-contract deployments, use foundry_script instead. 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 foundry_create? +

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

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

Can I rate-limit foundry_create? +

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

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

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