New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

prepare_uniswap_v3_burn

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...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
Critical RISK CLASS
Category Destructive
Parameters 32 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-uniswap-v3-burn.md

What prepare_uniswap_v3_burn does on VaultPilot MCP

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.

ParameterTypeRequiredDescription
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.

Why prepare_uniswap_v3_burn is rated Critical

This tool irreversibly destroys a Uniswap V3 LP position NFT, which represents a financial asset. The destruction cannot be undone—the position and its associated liquidity provision rights are permanently eliminated. While the tool includes safeguards (requiring full drainage before burn), the core operation is irreversible destruction of a financial asset, making it Destructive rather than merely Execute or Write.

From the tool's definition Tool description explicitly states it "destroys the position NFT (irreversible)" and uses the word "burn" which in blockchain contexts means permanent destruction. The description emphasizes this is part of an irreversible close-out sequence.

Questions about prepare_uniswap_v3_burn

What does the prepare_uniswap_v3_burn tool do? +

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.

What parameters does prepare_uniswap_v3_burn accept? +

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.

How do I enforce a policy on prepare_uniswap_v3_burn? +

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.

What risk level is prepare_uniswap_v3_burn? +

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.

Can I rate-limit prepare_uniswap_v3_burn? +

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.

How do I block prepare_uniswap_v3_burn completely? +

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.

What MCP server provides prepare_uniswap_v3_burn? +

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.

More on VaultPilot, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultPilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.