binance_us_cust_settlement_settings
Get current settlement settings for custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Shows automatic settlement configuration and schedule. Response includes: - settlementActive: Whether auto-settlement is enabled - frequencyInHours: Settlement frequency (e.g., 24 hours) - nextTriggerTi...
This record as markdown: /tools/nirholas-binance-mcp/binance-us-cust-settlement-settings.md
What binance_us_cust_settlement_settings does on Binance MCP Server
AI agents call binance_us_cust_settlement_settings 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_settings is rated Low
This tool retrieves custodial settlement configuration data. While it is fundamentally a Read operation (no data modification), the elevated severity from 'low' to 'medium' reflects that the response contains financial infrastructure details (settlement schedules, trigger times) for a custodial account.
From the tool's definition Tool name contains 'settings' and description states 'Get current settlement settings' and 'Shows automatic settlement configuration and schedule.' This is a retrieval operation that queries existing configuration without modification.
Attacks that exploit this kind of access
The rule that runs binance_us_cust_settlement_settings 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_settings, this is the rule to start with:
binance_us_cust_settlement_settings 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_settings call is checked against it from then on.
Questions about binance_us_cust_settlement_settings
Get current settlement settings for custodial solution. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY Shows automatic settlement configuration and schedule. Response includes: - settlementActive: Whether auto-settlement is enabled - frequencyInHours: Settlement frequency (e.g., 24 hours) - nextTriggerTime: Timestamp of next scheduled settlement. 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_settings: 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_settings 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_settings 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_settings. 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_settings 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