binance_us_cl_alert_history
Get margin call and liquidation alert 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 alert records including: - alertTime: When the alert was triggered - alertType: M...
This record as markdown: /tools/nirholas-binance-us-mcp/binance-us-cl-alert-history.md
What binance_us_cl_alert_history does on Binance US MCP Server
AI agents call binance_us_cl_alert_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_cl_alert_history is rated Low
This tool queries historical alert data from a margin/credit line account. While it accesses sensitive financial account information, it does not execute trades, move funds, or modify any account state—it only retrieves historical records.
From the tool's definition Tool description states it retrieves 'alert history' and 'returns alert records' including historical data about margin calls and liquidation alerts.
Attacks that exploit this kind of access
The rule that runs binance_us_cl_alert_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_cl_alert_history, this is the rule to start with:
binance_us_cl_alert_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_cl_alert_history call is checked against it from then on.
Questions about binance_us_cl_alert_history
Get margin call and liquidation alert 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 alert records including: - alertTime: When the alert was triggered - alertType: MARGIN_CALL or LIQUIDATION_CALL - currentLTV: LTV ratio at time of alert - All LTV thresholds for reference - totalBalance: Total collateral value at time of alert - loanAssets: Borrowed assets at time of alert - balances: Collateral balances at time of alert Use this to monitor your 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_alert_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_alert_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_alert_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_alert_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_alert_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