Create a new liquidity pool on Osmosis
AI agents use create-pool to create or update resources in Osmosis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Osmosis MCP Server environment.
The tool creates a new liquidity pool, which is a Write operation (creates/modifies data reversibly at the data structure level). While this involves blockchain transactions and financial implications, the primary action is pool creation rather than moving funds directly. Classified as Write rather than Financial because it creates infrastructure (a pool) rather than transferring value.
From the tool's definition Tool name 'create-pool' and description 'Create a new liquidity pool on Osmosis' indicate creation of new blockchain data structure. Sibling tools include 'create-gauge' and 'create-cosmwasm-pool', which are similarly Write operations.
Attacks that exploit this kind of access
Create a new liquidity pool on Osmosis. It is categorised as a Write tool in the Osmosis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for create-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.
create-pool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-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 create-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.
create-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 →