Critical Risk →

create_payment_onchain

🚨 CRITICAL RULE #1 - EXPIRATION: YOU MUST tell user payment expires in EXACTLY

How to control create_payment_onchain ↓

AI agents use create_payment_onchain 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

Creating on-chain payments commits financial obligations and moves value. Even though the description is incomplete (appears truncated at 'EXACTLY'), the tool name and server context clearly indicate irreversible financial commitment. This ranks highest in severity hierarchy: Financial > Destructive > Execute > Write > Read.

From the tool's definition Tool name 'create_payment_onchain' explicitly involves creating payments on-chain; paired with server description stating it 'enables users to manage wallets, execute token transactions'—this is a direct financial operation.

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

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

Any call to create_payment_onchain 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 create_payment_onchain tool do? +

🚨 CRITICAL RULE #1 - EXPIRATION: YOU MUST tell user payment expires in EXACTLY. 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 create_payment_onchain? +

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

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

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

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

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