binance_us_cust_transfer
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...
This record as markdown: /tools/nirholas-binance-mcp/binance-us-cust-transfer.md
What binance_us_cust_transfer does on Binance MCP Server
AI agents use binance_us_cust_transfer to commit financial operations through Binance MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why binance_us_cust_transfer is rated Critical
This tool moves money (crypto assets) and commits financial obligations by transferring funds between custodial accounts. The blast radius is critical because unauthorized transfers could result in immediate loss of user assets. Even with proper API key restrictions, misconfigured or compromised credentials could enable significant financial theft.
From the tool's definition Tool name 'binance_us_cust_transfer' combined with description: 'Transfer assets from custodial partner account to Binance.US custodial sub-account' and 'move assets from your custodial partner...to your Binance.US custodial sub-account for trading.' This is…
Attacks that exploit this kind of access
The rule that runs binance_us_cust_transfer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binance_us_cust_transfer, this is the rule to start with:
Any call to binance_us_cust_transfer is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every binance_us_cust_transfer call is checked against it from then on.
Questions about binance_us_cust_transfer
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 MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Binance 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 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 MCP Server MCP server (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
Across the catalogue