contract_deploy · Run402 MCP: Risk & Policy

WHAT IT DOES

What contract_deploy does on Run402

AI agents invoke contract_deploy to trigger actions in Run402. 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 contract_deploy needs a policy

Deploying smart contracts constitutes code execution with external side effects that are blockchain-permanent. While this could be considered Financial (given the blockchain context), the primary risk is Execute—the tool runs arbitrary contract code on a blockchain.

From the tool's definition Tool deploys a smart contract and signs a contract-creation transaction. The description states it 'signs a contract-creation tx' which indicates execution of blockchain operations that trigger external effects (contract deployment on-chain).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

contract_deploy Rate-limited

contract_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": {
    "contract_deploy": {
      "limits": [
        {
          "counter": "contract_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 Run402, so you can run agents against it safely.

FAQ

Questions about contract_deploy

What does the contract_deploy tool do? +

Deploy a smart contract from a KMS signer (signs a contract-creation tx with. It is categorised as a Execute tool in the Run402 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on contract_deploy? +

Register the Run402 MCP server in PolicyLayer and add a rule for contract_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 Run402. Nothing to install.

What risk level is contract_deploy? +

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

Can I rate-limit contract_deploy? +

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

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

contract_deploy is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.