Get transfer history for your credit line account. ⚠️ REQUIRES CREDIT LINE API KEY - Standard API keys will not work. ⚠️ Requires institutional credit line agreement with Binance.US. Returns transfer records including: - transferId: Unique transfer identifier - transferType: TRANSFER_IN or TRANSF...
AI agents call binance_us_cl_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.
This tool only retrieves historical transfer records (transferId, transferType, asset, amount, status, transferTime). It performs a read/query operation with no side effects — it does not initiate transfers or modify any data.
From the tool's definition Get transfer history for your credit line account... Use this to track deposits and withdrawals from your credit line account.
Documented attack patterns abuse exactly the kind of access binance_us_cl_transfer_history gives an agent:
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_cl_transfer_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cl_transfer_history": {}
}
}binance_us_cl_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 transfer history for your credit line account. ⚠️ REQUIRES CREDIT LINE API KEY - Standard API keys will not work. ⚠️ Requires institutional credit line agreement with Binance.US. Returns transfer records including: - transferId: Unique transfer identifier - transferType: TRANSFER_IN or TRANSFER_OUT - asset: Asset that was transferred - amount: Amount transferred - status: SUCCESS, PENDING, or FAIL - transferTime: When the transfer occurred Use this to track deposits and withdrawals from your credit line account. It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_cl_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.
binance_us_cl_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_cl_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_cl_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_cl_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.
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.
Free to start. No card required.
93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.