prepare-cl-remove-liquidity

Prepares a transaction to remove liquidity from a CL position

Server Osmosis MCP Server myronkoch-dev/mcp-osmosis
Category Destructive
Risk class Critical
Parameters 00 required

What prepare-cl-remove-liquidity does on Osmosis MCP Server

AI agents call prepare-cl-remove-liquidity to permanently remove resources in Osmosis MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why prepare-cl-remove-liquidity needs a policy

Removing liquidity from a concentrated liquidity (CL) position destroys or reduces that position permanently. While the assets are returned to the user, the position itself (or its liquidity) is irreversibly reduced or eliminated. This is more Destructive than Write since the position state cannot simply be undone. The blast radius is high because misuse could drain a user's entire liquidity position.

From the tool's definition 'remove liquidity from a CL position' — removing liquidity from a concentrated liquidity position is an irreversible action that withdraws assets and may close/destroy the position.

Questions about prepare-cl-remove-liquidity

What does the prepare-cl-remove-liquidity tool do? +

Prepares a transaction to remove liquidity from a CL position. It is categorised as a Destructive tool in the Osmosis MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on prepare-cl-remove-liquidity? +

Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for prepare-cl-remove-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.

What risk level is prepare-cl-remove-liquidity? +

prepare-cl-remove-liquidity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit prepare-cl-remove-liquidity? +

Yes. Add a rate_limit block to the prepare-cl-remove-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.

How do I block prepare-cl-remove-liquidity completely? +

Set action: deny in the PolicyLayer policy for prepare-cl-remove-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.

What MCP server provides prepare-cl-remove-liquidity? +

prepare-cl-remove-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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.