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 Binance US MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly moves financial assets (cryptocurrency) from one account to another. While it may not involve fiat currency conversion, it commits financial obligations and transfers value between custodial accounts, making it Financial rather than Write. The high severity reflects the potential for significant asset loss if misused by an AI agent with unauthorized access to custodial API keys.
From the tool's definition Transfer assets from custodial partner account to Binance.US custodial sub-account. Response includes asset, amount, transferId, and status — this moves cryptocurrency assets between accounts.
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 Binance US MCP Server, 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 Binance US MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Binance US MCP Server 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 Binance US MCP Server. 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 Binance US MCP Server MCP server (nirholas/binance-us-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance US MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.