Get lending events filtered by event type
AI agents call get_events_by_type 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.
This tool retrieves historical or current lending event data filtered by type. It queries existing information without creating, modifying, deleting, or executing any transactions. Even in a DeFi context, reading event data poses minimal risk—the worst case is an AI agent could gather market intelligence, but cannot commit funds or trigger financial transactions.
From the tool's definition Tool name 'get_events_by_type' and description 'Get lending events filtered by event type' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get lending events filtered by event type. It is categorised as a Read tool in the DeFi Rates MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DeFi Rates MCP Server MCP server in PolicyLayer and add a rule for get_events_by_type: 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.
get_events_by_type 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_events_by_type 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_events_by_type. 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_events_by_type 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.
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 →