Transfer assets from custodial partner account to Binance.US custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Use this to move assets from your custodial partner (e.g., Anchorage) to your Binance.US custodial sub-account for trading. Response includes: - asset: Transferred asset - am...
AI agents use binance_us_cust_transfer 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 moves assets between financial accounts, which is inherently a financial operation. The tool explicitly transfers cryptocurrency/assets from one custodial account to another, committing financial obligations and moving value. The requirement for a custodial API key and the inclusion of amount, asset, and transfer tracking confirms this is a money-movement operation.
From the tool's definition Transfer assets from custodial partner account to Binance.US custodial sub-account. Response includes asset, amount, transferId, and status. Requires CUSTODIAL SOLUTION API KEY.
Documented attack patterns abuse exactly the kind of access binance_us_cust_transfer 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 binance_us_cust_transfer:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cust_transfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to binance_us_cust_transfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer assets from custodial partner account to Binance.US custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Use this to move assets from your custodial partner (e.g., Anchorage) to your Binance.US custodial sub-account for trading. Response includes: - asset: Transferred asset - amount: Transfer amount - transferId: Unique transfer identifier - custodyAccountId/custodyAccountName: Custodian account details - status: Transfer status - createTime: Transfer creation timestamp. 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 binance_us_cust_transfer: 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.
binance_us_cust_transfer 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 binance_us_cust_transfer 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 binance_us_cust_transfer. 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.
binance_us_cust_transfer 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.