Get your LP token balance and the underlying token values for a Fee AMM pool.
AI agents call get_lp_position 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.
This tool retrieves information about liquidity provider positions in a decentralized finance context. It performs a read-only query of blockchain state (LP token balance and underlying values) with no side effects. While the server overall handles financial operations, this specific tool is strictly informational.
From the tool's definition Tool description states 'Get your LP token balance and the underlying token values' — this is a retrieval operation that queries data about an LP position without modifying state. No payment, deletion, or code execution occurs.
Documented attack patterns abuse exactly the kind of access get_lp_position gives an agent:
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_lp_position:
{
"version": "1",
"default": "deny",
"tools": {
"get_lp_position": {}
}
} get_lp_position is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get your LP token balance and the underlying token values for a Fee AMM pool. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.
Register the Tempo MCP server in PolicyLayer and add a rule for get_lp_position: 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.
get_lp_position 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_lp_position 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_lp_position. 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_lp_position 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.
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.