get_liquidations

Recent liquidation events with liquidator, liquidatee, collateral asset, and profit amounts. Optionally filter by market.

Server Graph Lending paulieb14/graph-lending-mcp
Category Read
Risk class Low
Parameters 00 required

What get_liquidations does on Graph Lending

AI agents call get_liquidations to retrieve information from Graph Lending without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_liquidations needs a policy

This is fundamentally a data retrieval tool that queries historical liquidation events across lending protocols. While the underlying liquidation events themselves represent financial transactions that already occurred on-chain, this tool only reads and returns structured data about those events—it does not trigger, execute, or modify any transactions.

From the tool's definition Tool name 'get_liquidations' and description indicate it 'retrieves...liquidation events' with filtering capability. The verb is 'get' (retrieves), and there are no modifications, deletions, or executions performed.

Questions about get_liquidations

What does the get_liquidations tool do? +

Recent liquidation events with liquidator, liquidatee, collateral asset, and profit amounts. Optionally filter by market. It is categorised as a Read tool in the Graph Lending MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_liquidations? +

Register the Graph Lending 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 Graph Lending. Nothing to install.

What risk level is get_liquidations? +

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

Can I rate-limit get_liquidations? +

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.

How do I block get_liquidations completely? +

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.

What MCP server provides get_liquidations? +

get_liquidations is provided by the Graph Lending MCP server (paulieb14/graph-lending-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.