Internal transfer between sub-account futures accounts. Move assets between different sub-account futures wallets.
AI agents use BinanceSubAccountFuturesTransfer 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 cryptocurrency assets between futures accounts, which constitutes a financial transaction. It commits financial obligations and transfers value. Even though it operates within sub-accounts (potentially limiting some blast radius), the irreversible nature of asset transfers and the potential for unauthorized fund movement make this critical severity.
From the tool's definition Tool name 'BinanceSubAccountFuturesTransfer' combined with description stating it performs 'Internal transfer between sub-account futures accounts' and 'Move assets between different sub-account futures wallets.' These are explicit financial operations…
Documented attack patterns abuse exactly the kind of access BinanceSubAccountFuturesTransfer 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 BinanceSubAccountFuturesTransfer:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceSubAccountFuturesTransfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to BinanceSubAccountFuturesTransfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Internal transfer between sub-account futures accounts. Move assets between different sub-account futures wallets. 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 BinanceSubAccountFuturesTransfer: 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.
BinanceSubAccountFuturesTransfer 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 BinanceSubAccountFuturesTransfer 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 BinanceSubAccountFuturesTransfer. 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.
BinanceSubAccountFuturesTransfer 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.