binance_us_cust_settlement_history
Get historical settlement records for custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Shows past automatic settlements to custodial partner. Response includes: - records: Array of settlement records - total: Total number of settlements Each record contains: - status: PROCESS, SUCCESS, ...
This record as markdown: /tools/nirholas-binance-mcp/binance-us-cust-settlement-history.md
What binance_us_cust_settlement_history does on Binance MCP Server
AI agents call binance_us_cust_settlement_history to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why binance_us_cust_settlement_history is rated Low
This is a read-only operation that retrieves historical settlement records from a custodial partner. While the Binance server as a whole includes financial and execute-class tools, this specific tool has no side effects: it does not move money, execute orders, modify data, or trigger new settlements.
From the tool's definition The tool "Get historical settlement records for custodial solution" retrieves and displays past settlement data including records, status, assets, and addresses.
Attacks that exploit this kind of access
The rule that runs binance_us_cust_settlement_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance 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_settlement_history, this is the rule to start with:
binance_us_cust_settlement_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every binance_us_cust_settlement_history call is checked against it from then on.
Questions about binance_us_cust_settlement_history
Get historical settlement records for custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Shows past automatic settlements to custodial partner. Response includes: - records: Array of settlement records - total: Total number of settlements Each record contains: - status: PROCESS, SUCCESS, or FAILURE - triggerTime: When settlement was triggered - settlementId: Unique settlement identifier - settlementAssets: Array of assets settled with amounts and addresses. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for binance_us_cust_settlement_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_cust_settlement_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_settlement_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_settlement_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_settlement_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.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue