Remove liquidity from a Fee AMM pool by burning LP tokens.
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.
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.
Documented attack patterns abuse exactly the kind of access remove_fee_liquidity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tempo, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_fee_liquidity:
{
"version": "1",
"default": "deny",
"hide": [
"remove_fee_liquidity"
]
} remove_fee_liquidity disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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.
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.
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.
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.
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.
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.
Start from Tempo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
61 Tempo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.