Build an unsigned Uniswap V3 LP burn transaction — destroys the position NFT (irreversible). Hard-refuses unless the position is fully drained: liquidity == 0 AND tokensOwed{0,1} == 0. Standard close-out sequence: prepare_uniswap_v3_decrease_liquidity({ liquidityPct: 100 }) → prepare_uniswap_v3_c...
AI agents call prepare_uniswap_v3_burn to permanently remove resources in VaultPilot MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | — | |
wallet | string | Yes | |
tokenId | string | Yes | ERC-721 tokenId of the LP NFT to destroy. Must be owned by `wallet`. The position must be fully drained: liquidity = 0 AND tokensOwed{0,1} = 0. Refused otherwis |
Parameters from the server's own tool schema.
An AI agent that decides to call prepare_uniswap_v3_burn doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from VaultPilot MCP is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
Build an unsigned Uniswap V3 LP burn transaction — destroys the position NFT (irreversible). Hard-refuses unless the position is fully drained: liquidity == 0 AND tokensOwed{0,1} == 0. Standard close-out sequence: prepare_uniswap_v3_decrease_liquidity({ liquidityPct: 100 }) → prepare_uniswap_v3_collect → prepare_uniswap_v3_burn. The error message names the right next step on each refusal. It is categorised as a Destructive tool in the VaultPilot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
prepare_uniswap_v3_burn accepts 3 parameters: chain, wallet, tokenId. Required: wallet, tokenId. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_uniswap_v3_burn: 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 VaultPilot MCP. Nothing to install.
prepare_uniswap_v3_burn 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 prepare_uniswap_v3_burn 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 prepare_uniswap_v3_burn. 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.
prepare_uniswap_v3_burn is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.