deploy_multi_contract · HashPilot MCP: Risk & Policy

WHAT IT DOES

What deploy_multi_contract does on HashPilot

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

Deploying smart contracts is an Execute action: it runs code on an external system (Hedera blockchain) whose effects are determined by the arguments provided (which contracts, their constructor parameters, and dependencies). While this tool does not directly transfer funds, it creates irreversible on-chain state and consumes gas/transaction fees.

From the tool's definition Tool description states "Deploy multiple contracts" and "Deploys in topological order" — these are executable operations that trigger external blockchain operations with effects dependent on arguments (contract code, constructor args, deployment order).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_multi_contract Rate-limited

deploy_multi_contract 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": {
    "deploy_multi_contract": {
      "limits": [
        {
          "counter": "deploy_multi_contract_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 deploy_multi_contract

What does the deploy_multi_contract tool do? +

Deploy multiple contracts with automatic dependency resolution. Supports $ContractName placeholders in constructor args for deployed contract addresses. Deploys in topological order based on dependencies. 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 deploy_multi_contract? +

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

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

Can I rate-limit deploy_multi_contract? +

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

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

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