Get liquidation events history across the platform.
AI agents call get_liquidation_history to retrieve information from Derive MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical liquidation event data from Lyra Finance's platform. The verb 'get' and the focus on historical data retrieval (not real-time triggers or state changes) confirm this is a Read operation. There are no side effects, no code execution, no data modification, and no financial transactions initiated by this tool itself—it passively returns existing records.
From the tool's definition Tool name 'get_liquidation_history' and description 'Get liquidation events history across the platform' indicate retrieval of historical data with no modification or execution of operations.
Attacks that exploit this kind of access
Get liquidation events history across the platform. It is categorised as a Read tool in the Derive MCP MCP Server, which means it retrieves data without modifying state.
Register the Derive MCP server in PolicyLayer and add a rule for get_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 Derive MCP. Nothing to install.
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 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_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 Derive MCP server (solenyaresearch0000/derive-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 →