List top Tinyman v2 liquidity pools on Algorand with TVL, volume, and token pair data.
AI agents call get_pools 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 is a straightforward read operation that queries and lists existing pool data from the Tinyman DEX. It retrieves informational metrics (TVL, volume, token pairs) with no side effects, no ability to modify state, and no execution of transactions. The low severity reflects minimal risk even if misused by an agent—returning public market data cannot cause harm.
From the tool's definition Tool name 'get_pools' and description 'List top Tinyman v2 liquidity pools' indicate data retrieval only. Returns TVL, volume, and token pair data—no state modification, no transaction execution, no financial operations.
Attacks that exploit this kind of access
List top Tinyman v2 liquidity pools on Algorand with TVL, volume, and token pair data. 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_pools: 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_pools 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_pools 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_pools. 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_pools 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 →