Get all liquidity pool positions for a wallet address. Returns pool details, token balances, and LP token amounts.
AI agents call get_lp_positions to retrieve information from Saros MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing liquidity pool position data from a wallet. It has no side effects—it does not create, modify, delete, or execute any operations. It falls squarely into the Read category as a straightforward data retrieval function.
From the tool's definition Tool name is 'get_lp_positions' and description states it 'Get all liquidity pool positions for a wallet address.
Attacks that exploit this kind of access
Get all liquidity pool positions for a wallet address. Returns pool details, token balances, and LP token amounts. It is categorised as a Read tool in the Saros MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Saros MCP Server MCP server in PolicyLayer and add a rule for get_lp_positions: 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 Saros MCP Server. Nothing to install.
get_lp_positions 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_positions 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_positions. 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_positions is provided by the Saros MCP Server MCP server (pavilion-devs/saros-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →