High Risk →

deploy_proxy

Deploy a proxy contract (UUPS or TransparentUpgradeableProxy) pointing to an implementation

How to control deploy_proxy ↓

AI agents invoke deploy_proxy 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 smart contracts to blockchain, which is an irreversible external operation with permanent on-chain effects. It executes code deployment whose consequences depend entirely on the proxy configuration and implementation address provided. While deployment itself is not destructive data deletion, it creates persistent blockchain state and financial implications (gas costs, security model establishment).

From the tool's definition deploy_proxy: Deploy a proxy contract (UUPS or TransparentUpgradeableProxy) pointing to an implementation

Documented attack patterns abuse exactly the kind of access deploy_proxy 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_proxy:

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

deploy_proxy 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_proxy tool do? +

Deploy a proxy contract (UUPS or TransparentUpgradeableProxy) pointing to an implementation. 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_proxy? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for deploy_proxy: 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_proxy? +

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

Can I rate-limit deploy_proxy? +

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

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

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