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...
AI agents call binance_us_cl_alert_history to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it queries historical alert data from a Binance.US credit line account without creating, modifying, or deleting data. However, severity is elevated to medium rather than low because: (1) it exposes sensitive financial account data (LTV ratios, collateral balances, loan details) that could be exploited if accessed by unauthorized actors; (2) it requires institutional-level Binance…
From the tool's definition Tool retrieves alert history records with no modification or side effects. Description states 'Get margin call and liquidation alert history' and 'Returns alert records including...' indicating a data retrieval operation.
Documented attack patterns abuse exactly the kind of access binance_us_cl_alert_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_cl_alert_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cl_alert_history": {}
}
}binance_us_cl_alert_history 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 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 BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain 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 BNB Chain MCP. 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 BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.