Critical Risk →

Send_BNB

đź’ŽTransfer native token (BNB), Before execution, check the wallet information first

How to control Send_BNB ↓

AI agents use Send_BNB to commit financial operations through BSC MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

This tool transfers BNB, a cryptocurrency with real monetary value, from a wallet to another address. This is a financial transaction that moves money on the Binance Smart Chain. Misuse by an AI agent could result in irreversible loss of funds, making it critical severity.

From the tool's definition Transfer native token (BNB)

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "Send_BNB": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to Send_BNB is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register BSC MCP Server — 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.
GATE THIS TOOL →

Free to start. No card required.

Go deeper

What does the Send_BNB tool do? +

đź’ŽTransfer native token (BNB), Before execution, check the wallet information first. It is categorised as a Financial tool in the BSC MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on Send_BNB? +

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

What risk level is Send_BNB? +

Send_BNB is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit Send_BNB? +

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

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

Send_BNB is provided by the BSC MCP Server MCP server (termix-official/bsc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BSC MCP Server tool call.

Deterministic rules across all 11 BSC MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 BSC MCP Server 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.