Get liquidation history for credit line account. ⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT Liquidations occur when LTV exceeds liquidationLTV threshold. This endpoint shows historical liquidation events. Each liquidation record may include: - Liquidated assets and amounts - Liquidation time...
AI agents call binance_us_cl_liquidation_history to retrieve information from Binance US MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is fundamentally a Read operation—it queries and retrieves data about past liquidation events without modifying state. However, severity is elevated to 'high' because: (1) access to liquidation history reveals sensitive institutional financial position and risk management details; (2) liquidation data could expose portfolio composition, leverage ratios (LTV), and fee structures; (3) misuse by an AI agent could…
From the tool's definition Tool retrieves historical liquidation events from a credit line account. Keywords: 'Get liquidation history', 'historical liquidation events', 'shows historical'. No creation, modification, deletion, or financial transactions occur—only querying past records.
Documented attack patterns abuse exactly the kind of access binance_us_cl_liquidation_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance US MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_cl_liquidation_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_cl_liquidation_history": {}
}
}binance_us_cl_liquidation_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 liquidation history for credit line account. ⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT Liquidations occur when LTV exceeds liquidationLTV threshold. This endpoint shows historical liquidation events. Each liquidation record may include: - Liquidated assets and amounts - Liquidation timestamp - LTV at time of liquidation - Fees charged Use this to: - Review past liquidation events - Understand liquidation patterns - Audit risk management effectiveness. 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_liquidation_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_liquidation_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_liquidation_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_liquidation_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_liquidation_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.
Start from Binance US 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.
93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.