Returns the type of a pool (balancer, stableswap, concentrated-liquidity)
AI agents call get-pool-type 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 is a straightforward read-only query that fetches immutable pool type information. The verb 'returns' and the lack of any modification language confirm it performs data retrieval only. Misuse by an AI agent would at worst return incorrect type information used in downstream logic, but causes no direct harm. Severity is low because the blast radius is limited to read operations on public blockchain data.
From the tool's definition Tool description states it 'Returns the type of a pool' — a query operation with no side effects. It retrieves metadata about an existing pool without modifying state.
Attacks that exploit this kind of access
Returns the type of a pool (balancer, stableswap, concentrated-liquidity). 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-type: 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-type 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-type 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-type. 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-type 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 →