Returns liquidity depth and distribution for a CL pool
AI agents call get-cl-pool-liquidity 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 performs a read-only query of blockchain state (liquidity information for a concentrated liquidity pool). It has no side effects, does not execute transactions, and does not modify or delete data. It falls squarely within the 'Read' category as a data retrieval operation. The low severity reflects minimal risk from misuse—an AI agent querying pool liquidity cannot cause harm.
From the tool's definition Tool name 'get-cl-pool-liquidity' and description 'Returns liquidity depth and distribution for a CL pool' indicate a query operation that retrieves pool data without modifying state.
Attacks that exploit this kind of access
Returns liquidity depth and distribution for a 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-pool-liquidity: 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-pool-liquidity 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-pool-liquidity 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-pool-liquidity. 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-pool-liquidity 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 →