Get detailed on-chain info for a Tinyman v2 pool by asset pair. Returns reserves, fees, LP supply, and pool status.
AI agents call get_pool 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 retrieves pool information from the Tinyman AMM DEX without creating, modifying, deleting, or executing any transactions. It is a pure read operation on blockchain data, making it the lowest risk category.
From the tool's definition Tool name 'get_pool' and description states it retrieves 'detailed on-chain info...Returns reserves, fees, LP supply, and pool status.' The verb 'Get' and 'Returns' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
Get detailed on-chain info for a Tinyman v2 pool by asset pair. Returns reserves, fees, LP supply, and pool status. 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: 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 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 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. 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 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 →