High Risk →

deploy_create2

Deploy a contract using CREATE2 for deterministic addresses across chains

How to control deploy_create2 ↓

AI agents invoke deploy_create2 to trigger actions in BNB Chain MCP. 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.

High Risk

This tool deploys arbitrary smart contracts to the blockchain, which is an irreversible execute action with severe blast radius. An AI agent with misuse could deploy malicious contracts, drain funds through exploits, or cause financial harm to users. While deployment itself is Execute-category, the potential financial impact and irreversibility elevate severity to critical.

From the tool's definition Tool name 'deploy_create2' and description 'Deploy a contract using CREATE2' indicate execution of smart contract deployment operations. CREATE2 is an Ethereum opcode for deterministic contract deployment.

Documented attack patterns abuse exactly the kind of access deploy_create2 gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy_create2:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_create2": {
      "limits": [
        {
          "counter": "deploy_create2_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the deploy_create2 tool do? +

Deploy a contract using CREATE2 for deterministic addresses across chains. It is categorised as a Execute tool in the BNB Chain MCP 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_create2? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for deploy_create2: 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 BNB Chain MCP. Nothing to install.

What risk level is deploy_create2? +

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

Can I rate-limit deploy_create2? +

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

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

deploy_create2 is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.