Get daily protocol stats (volume, trades, fees, splits, merges, redemptions) across both market types as a time series.
AI agents call get_daily_protocol_stats 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 performs a read-only query of on-chain market data. It retrieves historical statistics and metrics without creating, modifying, executing code, deleting data, or moving funds. The blast radius of misuse is minimal—an agent could only over-query or access data already public on-chain.
From the tool's definition Tool queries subgraphs for 'daily protocol stats (volume, trades, fees, splits, merges, redemptions) as a time series' — retrieves on-chain data with no modification or execution capability.
Attacks that exploit this kind of access
Get daily protocol stats (volume, trades, fees, splits, merges, redemptions) across both market types as a time series. 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_daily_protocol_stats: 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_daily_protocol_stats 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_daily_protocol_stats 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_daily_protocol_stats. 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_daily_protocol_stats 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 →