remove_liquidity
AI agents call remove_liquidity to permanently remove resources in Paloma DEX MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing liquidity from a DEX pool irreversibly withdraws deposited capital and is a destructive financial action that cannot be easily undone if executed incorrectly. The AI agent could drain liquidity positions, causing loss of user funds. This ranks as Destructive (irreversible) and Financial simultaneously; Destructive takes precedence per severity hierarchy.
From the tool's definition Tool named 'remove_liquidity' on a DEX trading server; paired with 'add_liquidity' indicating financial pool operations.
Attacks that exploit this kind of access
remove_liquidity. It is categorised as a Destructive tool in the Paloma DEX MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Paloma DEX MCP Server 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 Paloma DEX MCP Server. 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 Paloma DEX MCP Server MCP server (volumefi/mcppadex). 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 →