binance_us_cust_wallet_transfer_history

ServerBinance US MCP Server
CategoryRead

How to control binance_us_cust_wallet_transfer_history ↓

WHAT IT DOES

What binance_us_cust_wallet_transfer_history does on Binance US MCP Server

AI agents call binance_us_cust_wallet_transfer_history to retrieve information from Binance US MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why binance_us_cust_wallet_transfer_history needs a policy

This tool only retrieves historical transfer records (transferId, asset, amount, status, timestamps). It performs no transactions, modifications, or deletions — it is a pure read/query operation. Severity is low because it only exposes historical data, though it does require a privileged API key.

From the tool's definition Get history of transfers from Binance.US exchange wallet to custodial sub-account

Documented attack patterns abuse exactly the kind of access binance_us_cust_wallet_transfer_history gives an agent:

POLICY

How to control binance_us_cust_wallet_transfer_history

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_wallet_transfer_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "binance_us_cust_wallet_transfer_history": {}
  }
}

binance_us_cust_wallet_transfer_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Binance US MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Binance US MCP Server tools

Financial binance_us_cancel_replace Cancel an existing order and place a new order on the same symbol atomically. This is usef Financial binance_us_cust_new_order Place a new trade order through the custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION AP Financial binance_us_new_oco Place a new OCO (One-Cancels-the-Other) order on Binance.US. OCO orders combine a limit or Financial binance_us_new_order Place a new trade order on Binance.US. Supports LIMIT, MARKET, STOP_LOSS, STOP_LOSS_LIMIT, Financial binance_us_cl_transfer Transfer assets in or out of your credit line account. ⚠️ REQUIRES CREDIT LINE API KEY - Financial binance_us_cust_transfer Transfer assets from custodial partner account to Binance.US custodial sub-account. ⚠️ RE Financial binance_us_cust_undo_transfer Undo a previous transfer from your custodial partner. ⚠️ REQUIRES CUSTODIAL SOLUTION API Financial binance_us_cust_wallet_transfer Transfer assets from Binance.US exchange wallet to custodial sub-account. ⚠️ REQUIRES CUS

All 93 Binance US MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about binance_us_cust_wallet_transfer_history

What does the binance_us_cust_wallet_transfer_history tool do? +

Get history of transfers from Binance.US exchange wallet to custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Response includes: - data: Array of transfer records - total: Total number of transfers Each transfer record contains: transferId, clientOrderId, asset, amount, status, createTime, updateTime. It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on binance_us_cust_wallet_transfer_history? +

Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_wallet_transfer_history: 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_history? +

binance_us_cust_wallet_transfer_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit binance_us_cust_wallet_transfer_history? +

Yes. Add a rate_limit block to the binance_us_cust_wallet_transfer_history 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_history completely? +

Set action: deny in the PolicyLayer policy for binance_us_cust_wallet_transfer_history. 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_history? +

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

Enforce policy on every Binance US MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.