Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet.
AI agents use transfer_native to commit financial operations through BNB Chain MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Transferring native tokens (cryptocurrencies) directly moves financial value and commits irreversible blockchain transactions. This is a Financial category tool because it moves money. Severity is critical due to the high blast radius: an AI agent with misuse could drain the wallet, transfer funds to attacker-controlled addresses, or authorize unintended transactions resulting in permanent loss of funds.
From the tool's definition Tool name and description: 'Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet.' - explicitly transfers value from the configured wallet to another address without reversibility.
Documented attack patterns abuse exactly the kind of access transfer_native 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:
{
"version": "1",
"default": "deny",
"tools": {
"transfer_native": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transfer_native is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet. 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.
Register the BNB Chain MCP server in PolicyLayer and add a rule for transfer_native: 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.
transfer_native is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the transfer_native 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.
Set action: deny in the PolicyLayer policy for transfer_native. 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.
transfer_native 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.
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.