get_lp_position
Get your LP token balance and the underlying token values for a Fee AMM pool.
This record as markdown: /tools/arome3-tempo-mcp/get-lp-position.md
What get_lp_position does on Tempo
AI agents call get_lp_position to retrieve information from Tempo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_lp_position is rated Low
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.
Attacks that exploit this kind of access
The rule that runs get_lp_position safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_lp_position, this is the rule to start with:
get_lp_position 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 Tempo, apply this rule, and every get_lp_position call is checked against it from then on.
Questions about get_lp_position
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.
More on Tempo, and thousands of servers like it.
This server
Across the catalogue