remove_fee_liquidity

Remove liquidity from a Fee AMM pool by burning LP tokens.

SERVERTempo SOURCEarome3/tempo-mcp

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/arome3-tempo-mcp/remove-fee-liquidity.md

WHAT IT DOES

What remove_fee_liquidity does on Tempo

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

RISK

Why remove_fee_liquidity is rated Critical

Burning LP tokens permanently removes liquidity and destroys the tokens themselves—this is an irreversible operation that cannot be undone. While it could be classified as Financial (it affects monetary assets), the destructive nature of token burning (permanent destruction rather than transfer) makes Destructive the more precise category.

From the tool's definition Tool description explicitly states 'Remove liquidity from a Fee AMM pool by burning LP tokens.' The action of burning LP tokens is irreversible and destroys financial assets.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_fee_liquidity safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_fee_liquidity, this is the rule to start with:

remove_fee_liquidity Hidden

remove_fee_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_fee_liquidity"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_fee_liquidity

What does the remove_fee_liquidity tool do? +

Remove liquidity from a Fee AMM pool by burning LP tokens. It is categorised as a Destructive tool in the Tempo 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_fee_liquidity? +

Register the Tempo MCP server in PolicyLayer and add a rule for remove_fee_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 Tempo. Nothing to install.

What risk level is remove_fee_liquidity? +

remove_fee_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_fee_liquidity? +

Yes. Add a rate_limit block to the remove_fee_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_fee_liquidity completely? +

Set action: deny in the PolicyLayer policy for remove_fee_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_fee_liquidity? +

remove_fee_liquidity is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo 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 →