Get historical trading volume for a specific Spectra pool. Returns timestamped buy/sell volume in USD. Use list_pools first to find pool addresses. Useful for assessing pool activity and liquidity depth before entering a position. Context: Volume alone doesn't indicate capital efficiency — $1M v...
Single-target operation
Part of the Spectra MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_pool_volume to retrieve information from Spectra without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_pool_volume only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_pool_volume:
rules:
- action: allowSee the full Spectra policy for all 25 tools.
Agents calling read-class tools like get_pool_volume have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get historical trading volume for a specific Spectra pool. Returns timestamped buy/sell volume in USD. Use list_pools first to find pool addresses. Useful for assessing pool activity and liquidity depth before entering a position. Context: Volume alone doesn't indicate capital efficiency — $1M volume in a $5M liquidity pool is very different from $1M in a $500K pool. Combine volume data with pool liquidity (from list_pools or get_pt_details) to assess real trading conditions. Output includes volume/liquidity ratio analysis when pool data is available. For individual transaction details and whale activity, use get_pool_activity instead. Use quote_trade to estimate price impact for a specific trade size.. It is categorised as a Read tool in the Spectra MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_pool_volume. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Spectra MCP server.
get_pool_volume 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_volume rule in your Intercept 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 Intercept policy for get_pool_volume. 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_volume is provided by the Spectra MCP server (spectra-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept