Get history of transfers from Binance.US exchange wallet to custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Returns transfer history with status, amounts, and timestamps.
How to control binance_us_custodial_wallet_transfer_history ↓
AI agents use binance_us_custodial_wallet_transfer_history to commit financial operations through Binance MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
binance_us_custodial_wallet_transfer_history moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Documented attack patterns abuse exactly the kind of access binance_us_custodial_wallet_transfer_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_custodial_wallet_transfer_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_custodial_wallet_transfer_history": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to binance_us_custodial_wallet_transfer_history is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Get history of transfers from Binance.US exchange wallet to custodial sub-account. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Returns transfer history with status, amounts, and timestamps. 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_custodial_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 MCP Server. Nothing to install.
binance_us_custodial_wallet_transfer_history 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_custodial_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.
Set action: deny in the PolicyLayer policy for binance_us_custodial_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.
binance_us_custodial_wallet_transfer_history 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.
Deterministic rules across all 734 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
734 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.