AI agents call get_trending_pools to retrieve information from Flow MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available information about trending liquidity pools on a DEX without modifying, executing, or deleting any data. It is purely informational and poses minimal risk even if invoked by an AI agent, as it cannot alter blockchain state, execute code, or cause financial transactions. The scope is limited to querying public pool data on the Flow EVM chain.
From the tool's definition Tool name 'get_trending_pools' and description 'Get trending pools info' indicate a retrieval operation with no side effects. The description specifies it queries trending pool information on kittypunch DEX, a read-only data retrieval action.
Attacks that exploit this kind of access
Get trending pools info on kittypunch dex in flow EVM mainnet, NOTE: This is tool for flow EVM chain not flow blockchain. It is categorised as a Read tool in the Flow MCP MCP Server, which means it retrieves data without modifying state.
Register the Flow 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 Flow 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 Flow MCP server (outblock/flow-mcp-monorepo). 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 →