get_liquidation_history

Get historical liquidation events

SERVERDerive MCP Server SOURCEaadarshvelu/derive-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/aadarshvelu-derive-mcp/get-liquidation-history.md

WHAT IT DOES

What get_liquidation_history does on Derive MCP Server

AI agents call get_liquidation_history to retrieve information from Derive MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_liquidation_history is rated Low

This tool performs a read-only query of historical financial data. Even though liquidation events have financial significance, the tool itself only retrieves already-occurred events; it does not create, modify, or execute any transactions or operations.

From the tool's definition Tool name is 'get_liquidation_history' and description states 'Get historical liquidation events'. This retrieves historical data with no side effects—it queries past liquidation information from the Derive API without creating, modifying, or deleting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_liquidation_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Derive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_liquidation_history, this is the rule to start with:

get_liquidation_history Allowed

get_liquidation_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_liquidation_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Derive MCP Server, apply this rule, and every get_liquidation_history call is checked against it from then on.

FAQ

Questions about get_liquidation_history

What does the get_liquidation_history tool do? +

Get historical liquidation events. It is categorised as a Read tool in the Derive MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_liquidation_history? +

Register the Derive MCP Server 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 Server. Nothing to install.

What risk level is get_liquidation_history? +

get_liquidation_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_liquidation_history? +

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.

How do I block get_liquidation_history completely? +

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.

What MCP server provides get_liquidation_history? +

get_liquidation_history is provided by the Derive MCP Server MCP server (aadarshvelu/derive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Derive MCP Server, and thousands of servers like it.

This server

All 15 Derive MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →