Low Risk

get_fee_pool_info

Get information about a Fee AMM liquidity pool including reserves, LP supply,

How to control get_fee_pool_info ↓

What get_fee_pool_info does on Tempo

AI agents call get_fee_pool_info to retrieve information from Tempo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_fee_pool_info needs a policy

This tool queries and returns information about a liquidity pool (reserves, LP supply) but does not execute financial transactions, modify state, or trigger external operations. It is purely informational, fitting the Read category. While the server handles financial payments, this specific tool only retrieves pool data, making it low-severity.

From the tool's definition Tool name is 'get_fee_pool_info' with description 'Get information about a Fee AMM liquidity pool including reserves, LP supply'. The verb 'Get information' explicitly indicates data retrieval without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_fee_pool_info gives an agent:

How to control get_fee_pool_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_fee_pool_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_fee_pool_info": {}
  }
}

get_fee_pool_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Tempo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_fee_pool_info

What does the get_fee_pool_info tool do? +

Get information about a Fee AMM liquidity pool including reserves, LP supply,. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_fee_pool_info? +

Register the Tempo MCP server in PolicyLayer and add a rule for get_fee_pool_info: 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 Tempo. Nothing to install.

What risk level is get_fee_pool_info? +

get_fee_pool_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_fee_pool_info? +

Yes. Add a rate_limit block to the get_fee_pool_info 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.

How do I block get_fee_pool_info completely? +

Set action: deny in the PolicyLayer policy for get_fee_pool_info. 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.

What MCP server provides get_fee_pool_info? +

get_fee_pool_info is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tempo tool call.

Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.