analyze_pool
Maps to GET /pools/analyze/:id. Returns real-time momentum data for a specific pool from GeckoTerminal: multi-timeframe volume (5m, 15m, 30m, 1h, 6h), price changes (5m–24h), buy/sell transaction counts, unique traders (24h), and reserve in USD. Data is cached for 10 minutes; stale entries are re...
This record as markdown: /tools/defire-business-swapwizard-mcp/analyze-pool.md
What analyze_pool does on Swapwizard
AI agents call analyze_pool to retrieve information from Swapwizard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | integer | Yes | Pool numeric ID (from the id field in search_liquidity_pools response) |
Parameters from the server's own tool schema.
Why analyze_pool is rated Low
This is a read-only query tool that retrieves and aggregates pool analytics data from GeckoTerminal. While it provides data relevant to DeFi decision-making, the tool itself performs no state changes, executes no transactions, moves no funds, and has minimal blast radius if misused by an AI agent—it would only return analytics data without triggering any on-chain or financial operations.
From the tool's definition Tool maps to GET /pools/analyze/:id and returns real-time momentum data including volume, price changes, transaction counts, unique traders, and reserves. No modification, deletion, execution of external operations, or financial transactions occur.
Attacks that exploit this kind of access
The rule that runs analyze_pool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Swapwizard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For analyze_pool, this is the rule to start with:
analyze_pool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Swapwizard, apply this rule, and every analyze_pool call is checked against it from then on.
Questions about analyze_pool
Maps to GET /pools/analyze/:id. Returns real-time momentum data for a specific pool from GeckoTerminal: multi-timeframe volume (5m, 15m, 30m, 1h, 6h), price changes (5m–24h), buy/sell transaction counts, unique traders (24h), and reserve in USD. Data is cached for 10 minutes; stale entries are refreshed on-demand. Use the numeric id field returned by search_liquidity_pools. It is categorised as a Read tool in the Swapwizard MCP Server, which means it retrieves data without modifying state.
analyze_pool accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Swapwizard MCP server in PolicyLayer and add a rule for analyze_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 Swapwizard. Nothing to install.
analyze_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 analyze_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 analyze_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.
analyze_pool is provided by the Swapwizard MCP server (@swapwizard/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Swapwizard, and thousands of servers like it.
This server
Across the catalogue