Critical Risk →

transfer_native_token

Transfer native tokens (BNB, ETH, MATIC, etc.) to an address

How to control transfer_native_token ↓

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

Critical Risk

This tool directly moves money (native blockchain tokens) from one account to another. While the action is technically reversible in the sense that a recipient could return funds, the transfer itself is an irreversible financial transaction that commits real value.

From the tool's definition Transfer native tokens (BNB, ETH, MATIC, etc.) to an address. The tool explicitly moves cryptocurrency to a recipient address, directly committing financial obligations and irreversibly transferring assets.

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

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

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

  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.
GATE THIS TOOL →

Free to start. No card required.

Go deeper

What does the transfer_native_token tool do? +

Transfer native tokens (BNB, ETH, MATIC, etc.) to an address. It is categorised as a Financial tool in the BNB Chain MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_native_token? +

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

transfer_native_token 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 transfer_native_token? +

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

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

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