remove_liquidity
Remove liquidity from a DragonSwap V3 position
This record as markdown: /tools/testinguser1111111-sei-mcp-server/remove-liquidity.md
What remove_liquidity does on SEI MCP Server V2
AI agents call remove_liquidity to permanently remove resources in SEI MCP Server V2, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_liquidity is rated Critical
An AI agent that decides to call remove_liquidity doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from SEI MCP Server V2 is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remove_liquidity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_liquidity, this is the rule to start with:
remove_liquidity is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every remove_liquidity call is checked against it from then on.
Questions about remove_liquidity
Remove liquidity from a DragonSwap V3 position. It is categorised as a Destructive tool in the SEI MCP Server V2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for 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 SEI MCP Server V2. Nothing to install.
remove_liquidity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
remove_liquidity is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SEI MCP Server V2, and thousands of servers like it.
Across the catalogue