Returns the total number of LP shares for a pool
AI agents call get-pool-total-shares to retrieve information from Osmosis 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 returns data about LP (liquidity provider) shares for a specific pool on the Osmosis blockchain. It performs no state changes, does not execute transactions, and does not have financial implications on its own. It is a simple informational query with minimal blast radius if misused—an AI could at worst retrieve unnecessary or sensitive pool data, but cannot create, modify, or delete anything.
From the tool's definition Tool name 'get-pool-total-shares' and description 'Returns the total number of LP shares for a pool' indicate a read-only query operation that retrieves pool data without modification or side effects.
Attacks that exploit this kind of access
Returns the total number of LP shares for a pool. It is categorised as a Read tool in the Osmosis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for get-pool-total-shares: 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 Osmosis MCP Server. Nothing to install.
get-pool-total-shares 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-total-shares 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-pool-total-shares. 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-total-shares is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). 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 →