get_recent_events

Get recent on-chain lending events (borrows, deposits, liquidations, repays). Returns real-time blockchain activity.

Server DeFi Rates MCP Server qingfeng/defi-rates-mcp
Category Read
Risk class Low
Parameters 00 required

What get_recent_events does on DeFi Rates MCP Server

AI agents call get_recent_events to retrieve information from DeFi Rates MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_recent_events needs a policy

This tool retrieves and queries real-time on-chain event data (borrows, deposits, liquidations, repays) from DeFi protocols. It performs no creation, modification, deletion, code execution, or financial transactions. While the context involves DeFi and financial protocols, the tool itself only reads event data without moving money, executing transactions, or triggering external operations.

From the tool's definition Tool description states 'Get recent on-chain lending events' and 'Returns real-time blockchain activity.' The verb 'Get' and the read-only nature of querying historical/recent blockchain events indicate data retrieval with no side effects.

Questions about get_recent_events

What does the get_recent_events tool do? +

Get recent on-chain lending events (borrows, deposits, liquidations, repays). Returns real-time blockchain activity. It is categorised as a Read tool in the DeFi Rates MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_events? +

Register the DeFi Rates MCP Server MCP server in PolicyLayer and add a rule for get_recent_events: 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 DeFi Rates MCP Server. Nothing to install.

What risk level is get_recent_events? +

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

Can I rate-limit get_recent_events? +

Yes. Add a rate_limit block to the get_recent_events 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_recent_events completely? +

Set action: deny in the PolicyLayer policy for get_recent_events. 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_recent_events? +

get_recent_events is provided by the DeFi Rates MCP Server MCP server (qingfeng/defi-rates-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.