AI agents call crypto.dex-token-pools to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries blockchain data about decentralized exchange liquidity pools. It has no side effects—it does not create, modify, delete, or execute any transactions. It is a read-only data lookup, comparable to a search or list operation. The 'pay-per-call' nature of the server is irrelevant to this tool's classification, as the tool itself does not process payments.
From the tool's definition Tool description states it 'Returns each pool' and queries existing DEX pool data by contract address via GeckoTerminal. The operation is a retrieval/lookup ('All DEX pools trading a given token') with no modification, deletion, or execution of transactions.
Attacks that exploit this kind of access
All DEX pools trading a given token, by contract address (via GeckoTerminal, free/keyless). Returns each pool\. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for crypto.dex-token-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 Mcp. Nothing to install.
crypto.dex-token-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 crypto.dex-token-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 crypto.dex-token-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.
crypto.dex-token-pools is provided by the MCP server (@2sio/mcp). 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 →