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-us-mcp/binance-us-cust-settlement-history.md
What binance_us_cust_settlement_history does on Binance US MCP Server
AI agents call binance_us_cust_settlement_history to retrieve information from Binance US 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 tool retrieves and queries historical settlement data without modifying, creating, or deleting anything. It is a pure read operation. Severity is high rather than low because: (1) it exposes sensitive financial settlement history including asset amounts and addresses tied to custodial accounts, (2) it requires a custodial solution API key, indicating access to institutional-grade financial infrastructure, and…
From the tool's definition Tool name contains 'history' and description states 'Get historical settlement records' and 'Shows past automatic settlements'.
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 US 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 US 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 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_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 US 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 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.
More on Binance US MCP Server, and thousands of servers like it.
This server
Across the catalogue