Query details for a specific pool on a network.
AI agents call get_pool_details 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.
This tool retrieves liquidity pool information from a DEX. It performs a read-only query operation with no capability to modify, execute external operations, delete data, or move funds. The blast radius of misuse is minimal—returning incorrect or excessive pool details poses no direct harm. It belongs in the Read category, with low severity.
From the tool's definition Tool name is 'get_pool_details' and description states 'Query details for a specific pool on a network.' The verb 'Query' and action 'get' both indicate data retrieval without modification or side effects.
Attacks that exploit this kind of access
Query details for a specific pool on a network. 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_pool_details: 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_pool_details 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_details 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_details. 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_details 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 →