deploy_contract · Neo N3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_contract does on Neo N3 MCP Server

AI agents invoke deploy_contract to trigger actions in Neo N3 MCP Server. 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_contract needs a policy

Contract deployment is an Execute action: it runs code (the smart contract) on an external system (Neo N3 blockchain) with effects dependent on the contract's logic. While this modifies blockchain state, it is reversible through redeployment or contract upgrades, distinguishing it from Destructive.

From the tool's definition Tool deploys smart contracts on blockchain, executing arbitrary code. Description states 'Deploy a smart contract from a NEF script and manifest', confirming it triggers external blockchain operations whose effects are determined by contract code arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_contract Rate-limited

deploy_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_contract": {
      "limits": [
        {
          "counter": "deploy_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 Neo N3 MCP Server, so you can run agents against it safely.

FAQ

Questions about deploy_contract

What does the deploy_contract tool do? +

Deploy a smart contract from a NEF script and manifest. Requires deployer WIF and explicit confirmation. It is categorised as a Execute tool in the Neo N3 MCP Server 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_contract? +

Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for deploy_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 Neo N3 MCP Server. Nothing to install.

What risk level is deploy_contract? +

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

Can I rate-limit deploy_contract? +

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

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

deploy_contract is provided by the Neo N3 MCP Server MCP server (r3e-network/neo-n3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.