get_trending_pools
AI agents call get_trending_pools to retrieve information from DEX Pools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to query and return trending pool information from a DEX data service. No write, execute, destructive, or financial operations are performed. The tool description is empty, which slightly reduces confidence, but the naming pattern and context of sibling read-only tools strongly indicate this is a data retrieval operation with no side effects.
From the tool's definition Tool name 'get_trending_pools' indicates a retrieval operation. Server description emphasizes 'real-time access to DEX liquidity pool data' and sibling tools (get_new_pools, get_pool_details, get_supported_dexes_by_network, etc.) are all data retrieval…
Attacks that exploit this kind of access
get_trending_pools. It is categorised as a Read tool in the DEX Pools MCP MCP Server, which means it retrieves data without modifying state.
Register the DEX Pools MCP server in PolicyLayer and add a rule for get_trending_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 DEX Pools MCP. Nothing to install.
get_trending_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_trending_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_trending_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_trending_pools is provided by the DEX Pools MCP server (kukapay/dex-pools-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 →