get_liquidations
Get real-time crypto liquidation data — long/short volume, cascade detection, biggest events. $0.005
This record as markdown: /tools/de-carbon-cashmere-api-crypto-intelligence/get-liquidations.md
What get_liquidations does on Crypto Intelligence
AI agents call get_liquidations to retrieve information from Crypto Intelligence without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
hours | integer | — | Lookback hours (1-24) |
Parameters from the server's own tool schema.
Why get_liquidations is rated Low
This tool retrieves and queries liquidation market data (volumes, events, detection metrics). It performs no side effects, does not execute trades, does not modify data, and does not delete anything. It is purely informational Read access. Severity is medium rather than low because liquidation data could inform high-impact trading decisions if misused by an agent, but the tool itself causes no direct harm.
From the tool's definition Tool name 'get_liquidations' and description 'Get real-time crypto liquidation data — long/short volume, cascade detection, biggest events' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs get_liquidations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crypto Intelligence, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_liquidations, this is the rule to start with:
get_liquidations 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 Crypto Intelligence, apply this rule, and every get_liquidations call is checked against it from then on.
Questions about get_liquidations
Get real-time crypto liquidation data — long/short volume, cascade detection, biggest events. $0.005. It is categorised as a Read tool in the Crypto Intelligence MCP Server, which means it retrieves data without modifying state.
get_liquidations accepts 1 parameter: hours. The full parameter table on this page comes from the server's own tool schema.
Register the Crypto Intelligence MCP server in PolicyLayer and add a rule for get_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 Crypto Intelligence. Nothing to install.
get_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 get_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 get_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.
get_liquidations is provided by the Crypto Intelligence MCP server (https://api.carbon-cashmere.de/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crypto Intelligence, and thousands of servers like it.
This server
Across the catalogue