Get liquidation history (futures only). Parameters: - base: Required, futures base currency. - quote: Optional, quote currency, default "USDT". - start_time: Optional, start timestamp (milliseconds). - end_time: Optional, end timestamp (milliseconds). - page: Optional, page number, default 1. - ...
Part of the Coinex MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_liquidation_history to retrieve information from Coinex without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_liquidation_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_liquidation_history:
rules:
- action: allowSee the full Coinex policy for all 12 tools.
Agents calling read-class tools like get_liquidation_history have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get liquidation history (futures only). Parameters: - base: Required, futures base currency. - quote: Optional, quote currency, default "USDT". - start_time: Optional, start timestamp (milliseconds). - end_time: Optional, end timestamp (milliseconds). - page: Optional, page number, default 1. - limit: Optional, number of records, default 100. Returns: {code, message, data}.. It is categorised as a Read tool in the Coinex MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_liquidation_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Coinex MCP server.
get_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 get_liquidation_history rule in your Intercept 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 Intercept policy for get_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.
get_liquidation_history is provided by the Coinex MCP server (helix-song/coinex_mcp_server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept