remove_liquidity

Remove liquidity from a Pendle market by burning LP tokens

SERVERWaiaas SOURCEminhoyoo-iotrust/waiaas

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/minhoyoo-iotrust-waiaas/remove-liquidity.md

WHAT IT DOES

What remove_liquidity does on Waiaas

AI agents call remove_liquidity to permanently remove resources in Waiaas, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_liquidity is rated Critical

Although the tool transfers assets back to the user (making it superficially similar to Write), the core mechanism is burning LP tokens, which is irreversible destruction of a financial instrument. Combined with the broader context of a wallet MCP server managing multi-chain crypto operations and financial assets, misuse could result in unintended liquidity removal and permanent loss of LP positions.

From the tool's definition 'Remove liquidity from a Pendle market by burning LP tokens' - the tool irreversibly burns LP tokens, converting them to underlying assets in a non-recoverable way. Burning is a destructive action that cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_liquidity safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Waiaas, 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 Hidden

remove_liquidity is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_liquidity"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Waiaas, apply this rule, and every remove_liquidity call is checked against it from then on.

FAQ

Questions about remove_liquidity

What does the remove_liquidity tool do? +

Remove liquidity from a Pendle market by burning LP tokens. It is categorised as a Destructive tool in the Waiaas 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 remove_liquidity? +

Register the Waiaas 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 Waiaas. Nothing to install.

What risk level is remove_liquidity? +

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 remove_liquidity? +

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.

How do I block remove_liquidity completely? +

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.

What MCP server provides remove_liquidity? +

remove_liquidity is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Waiaas, and thousands of servers like it.

This server

All 126 Waiaas tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →