Perp liquidation data across OKX for BTC/ETH/SOL/AVAX/LINK/ARB. Signal-first: LONG_CASCADE/SHORT_CASCADE/BALANCED/EXTREME. Shows long vs short liquidation volume, biggest single events, hottest price zones. Pairs with funding_rates() and open_interest() for complete positioning picture. Higher-si...
AI agents call liquidations to retrieve information from Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical and current liquidation data from cryptocurrency exchanges—a read operation that retrieves market intelligence. While the data relates to financial markets and could inform trading decisions, the tool itself does not execute trades, move funds, or modify data.
From the tool's definition Tool retrieves and displays 'Perp liquidation data across OKX' including 'long vs short liquidation volume, biggest single events, hottest price zones.' The description indicates data retrieval and analysis (querying liquidation events and metrics) with no…
Attacks that exploit this kind of access
Perp liquidation data across OKX for BTC/ETH/SOL/AVAX/LINK/ARB. Signal-first: LONG_CASCADE/SHORT_CASCADE/BALANCED/EXTREME. Shows long vs short liquidation volume, biggest single events, hottest price zones. Pairs with funding_rates() and open_interest() for complete positioning picture. Higher-signal than OI or funding rates — shows what has already been forced out. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for liquidations: 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 Mcp Server. Nothing to install.
liquidations 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 liquidations 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 liquidations. 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.
liquidations is provided by the Mcp Server MCP server (Homie4570/lso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →