Get a unified feed of all recent on-chain activity: trades, splits, merges, and redemptions across both market types with market names.
AI agents call get_recent_activity 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 queries blockchain subgraphs to fetch and display historical activity records (trades, splits, merges, redemptions). It has no side effects, does not execute code or transactions, does not modify state, and does not delete or move funds. The blast radius of misuse is minimal—at worst, an agent could request excessive data, causing rate-limiting or DoS, but no data integrity or financial risk exists.
From the tool's definition Tool name and description indicate retrieval only: 'Get a unified feed of all recent on-chain activity' is a query operation that retrieves and presents existing on-chain data without modification.
Attacks that exploit this kind of access
Get a unified feed of all recent on-chain activity: trades, splits, merges, and redemptions across both market types with market names. 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_recent_activity: 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_recent_activity 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_recent_activity 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_recent_activity. 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_recent_activity 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 →