Transfer assets from one sub-account to another sub-account. Both accounts must belong to the same master account.
AI agents use BinanceSubAccountTransferToSub to commit financial operations through BNB Chain MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves financial assets (cryptocurrency or tokens on BNB Chain) between accounts. Even though transfers are technically reversible via counter-transfers, the immediate effect is to commit a financial obligation and change asset allocation. This meets the definition of Financial category.
From the tool's definition Tool name and description explicitly state 'Transfer assets from one sub-account to another sub-account.' The term 'Transfer assets' in a financial context means moving money/tokens between accounts, which constitutes a financial operation.
Documented attack patterns abuse exactly the kind of access BinanceSubAccountTransferToSub 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 BinanceSubAccountTransferToSub:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceSubAccountTransferToSub": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to BinanceSubAccountTransferToSub is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer assets from one sub-account to another sub-account. Both accounts must belong to the same master account. 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 BinanceSubAccountTransferToSub: 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.
BinanceSubAccountTransferToSub 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 BinanceSubAccountTransferToSub 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 BinanceSubAccountTransferToSub. 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.
BinanceSubAccountTransferToSub 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.