Get analytics data for a Tinyman pool by its address, including volume, TVL, and fees.
AI agents call get_pool_analytics to retrieve information from Tinyman MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns analytics metrics (volume, total value locked, fees) for a specified pool. It performs no state changes, does not execute transactions, does not move funds, and does not irreversibly modify any data. It is a straightforward read operation on pool analytics data.
From the tool's definition Tool description explicitly states it retrieves 'analytics data for a Tinyman pool by its address, including volume, TVL, and fees.' The action is purely data retrieval with no modification or execution capabilities.
Attacks that exploit this kind of access
Get analytics data for a Tinyman pool by its address, including volume, TVL, and fees. It is categorised as a Read tool in the Tinyman MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tinyman MCP Server MCP server in PolicyLayer and add a rule for get_pool_analytics: 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 Tinyman MCP Server. Nothing to install.
get_pool_analytics 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_pool_analytics 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_pool_analytics. 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_pool_analytics is provided by the Tinyman MCP Server MCP server (nautilusoss/tinymanmcp). 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 →