binance_us_cust_wallet_transfer

SERVERBinance US MCP Server SOURCEnirholas/binance-us-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-binance-us-mcp/binance-us-cust-wallet-transfer.md

WHAT IT DOES

What binance_us_cust_wallet_transfer does on Binance US MCP Server

AI agents use binance_us_cust_wallet_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.

RISK

Why binance_us_cust_wallet_transfer is rated Critical

This tool directly moves cryptocurrency assets (financial value) between accounts. While asset transfers are reversible in principle, they represent immediate commitments of financial value and could result in unintended loss of funds if an AI agent misuses parameters (wrong recipient, excessive amounts). The Financial category applies because the tool commits cryptocurrency holdings to specific accounts.

From the tool's definition Tool transfers assets from exchange wallet to custodial sub-account. Description states 'Transfer assets from Binance.US exchange wallet to custodial sub-account' and requires 'CUSTODIAL SOLUTION API KEY'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs binance_us_cust_wallet_transfer safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Binance US 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_wallet_transfer, this is the rule to start with:

binance_us_cust_wallet_transfer Approval-gated

Any call to binance_us_cust_wallet_transfer is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "binance_us_cust_wallet_transfer": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Binance US MCP Server, apply this rule, and every binance_us_cust_wallet_transfer call is checked against it from then on.

FAQ

Questions about binance_us_cust_wallet_transfer

What does the binance_us_cust_wallet_transfer tool do? +

Transfer assets from Binance.US exchange wallet to custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Use this to move assets from your Binance.US exchange wallet to your custodial sub-account for trading. Response includes: - asset: Transferred asset - amount: Transfer amount - clientOrderId: Your reference ID (or auto-generated) - transferId: Unique transfer identifier - status: Transfer status (SUCCESS, PENDING, etc.) - 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.

How do I enforce a policy on binance_us_cust_wallet_transfer? +

Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_wallet_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.

What risk level is binance_us_cust_wallet_transfer? +

binance_us_cust_wallet_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit binance_us_cust_wallet_transfer? +

Yes. Add a rate_limit block to the binance_us_cust_wallet_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.

How do I block binance_us_cust_wallet_transfer completely? +

Set action: deny in the PolicyLayer policy for binance_us_cust_wallet_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.

What MCP server provides binance_us_cust_wallet_transfer? +

binance_us_cust_wallet_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.

KEEP EXPLORING

More on Binance US MCP Server, and thousands of servers like it.

This server

All 93 Binance US MCP Server tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge →transfer_sites on A3plus →export_wallet on Conviction → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →