Get history of transfers from custodial partner to Binance.US custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Includes ExpressTrade transfers, Custodian transfers, and Undo transfers. Response includes: - data: Array of transfer records - total: Total number of transfers Each record...
AI agents call binance_us_cust_transfer_history to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transfer records and does not initiate any transactions or move funds. It is a read-only query of transfer history. However, severity is medium because it exposes sensitive financial account data including transfer amounts, asset types, and custodial account details, which could be misused if accessed by an unauthorized agent.
From the tool's definition Get history of transfers from custodial partner to Binance.US custodial sub-account
Documented attack patterns abuse exactly the kind of access binance_us_cust_transfer_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_cust_transfer_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cust_transfer_history": {}
}
}binance_us_cust_transfer_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get history of transfers from custodial partner to Binance.US custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Includes ExpressTrade transfers, Custodian transfers, and Undo transfers. Response includes: - data: Array of transfer records - total: Total number of transfers Each record contains: transferId, clientOrderId, asset, amount, status, expressTrade flag, createTime, updateTime. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
binance_us_cust_transfer_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the binance_us_cust_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.
Set action: deny in the PolicyLayer policy for binance_us_cust_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.
binance_us_cust_transfer_history is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI 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.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.