Returns all positions in a specific CL pool
AI agents call get-cl-positions-by-pool 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 queries and returns existing position data from a concentrated liquidity (CL) pool. It performs no state changes, has no side effects, and poses minimal risk if misused by an AI agent. The worst case is retrieving information that may be publicly available on-chain anyway.
From the tool's definition Tool name 'get-cl-positions-by-pool' and description 'Returns all positions in a specific CL pool' indicate a query operation that retrieves data without modification.
Attacks that exploit this kind of access
Returns all positions in a specific CL 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-cl-positions-by-pool: 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-cl-positions-by-pool 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-cl-positions-by-pool 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-cl-positions-by-pool. 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-cl-positions-by-pool 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 →