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...
AI agents call binance_us_cust_settlement_settings to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration and status information about settlement settings without modifying any data or executing transactions. Although it involves financial infrastructure (settlement operations), the tool itself only reads existing settings and does not move money, commit financial obligations, or trigger settlement actions—it merely displays their current configuration.
From the tool's definition Tool name 'binance_us_cust_settlement_settings' and description 'Get current settlement settings' and 'Shows automatic settlement configuration and schedule' indicate data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access binance_us_cust_settlement_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_cust_settlement_settings:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cust_settlement_settings": {}
}
}binance_us_cust_settlement_settings 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 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 Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI 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 Sperax Ecosystem Crypto & DeFI 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 Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI 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.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.