Get splits, merges, and redemptions — the liquidity lifecycle events. Filter by market or user address.
AI agents call get_liquidity_events to retrieve information from Limitless MCP 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 liquidity event data (splits, merges, redemptions) from subgraphs with optional filtering by market or user address. It performs no writes, executions, or destructive operations—purely informational queries. Low severity due to read-only nature with no side effects.
From the tool's definition Tool name 'get_liquidity_events' and description 'Get splits, merges, and redemptions' indicate data retrieval only. No mutations, deletions, or state changes. Queries on-chain data per server description.
Attacks that exploit this kind of access
Get splits, merges, and redemptions — the liquidity lifecycle events. Filter by market or user address. It is categorised as a Read tool in the Limitless MCP MCP Server, which means it retrieves data without modifying state.
Register the Limitless MCP server in PolicyLayer and add a rule for get_liquidity_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 Limitless MCP. Nothing to install.
get_liquidity_events 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_liquidity_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.
Set action: deny in the PolicyLayer policy for get_liquidity_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.
get_liquidity_events is provided by the Limitless MCP server (paulieb14/limitless-subgraphs). 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 →