Build an unsigned Uniswap V3 LP decreaseLiquidity transaction — removes liquidity from an existing position by tokenId. Pass liquidityPct: 100 for a full close-out (typical follow-up: prepare_uniswap_v3_collect, then optionally prepare_uniswap_v3_burn). Pass liquidity: "<raw>" for exact-amount ac...
AI agents invoke prepare_uniswap_v3_decrease_liquidity to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | — | |
wallet | string | Yes | |
tokenId | string | Yes | ERC-721 tokenId of the LP NFT to decrease liquidity from. Must be owned by `wallet`. |
liquidity | string | — | Raw liquidity to withdraw (decimal-string bigint). Use when you need exact accounting; otherwise prefer liquidityPct. Mutually exclusive with `liquidityPct`. |
deadlineSec | integer | — | |
slippageBps | integer | — | Slippage tolerance in bps. Default 50; soft cap 100. |
liquidityPct | integer | — | Percentage of position liquidity to withdraw (1-100). Pass 100 for full close-out (typical follow-up: prepare_uniswap_v3_collect, then optionally burn). Mutuall |
acknowledgeHighSlippage | boolean | — |
Parameters from the server's own tool schema.
prepare_uniswap_v3_decrease_liquidity triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Build an unsigned Uniswap V3 LP decreaseLiquidity transaction — removes liquidity from an existing position by tokenId. Pass liquidityPct: 100 for a full close-out (typical follow-up: prepare_uniswap_v3_collect, then optionally prepare_uniswap_v3_burn). Pass liquidity: "<raw>" for exact-amount accounting; the two args are mutually exclusive. Hard-refuses when the tokenId is not owned by wallet (would credit the actual owner) and when the position has zero liquidity (nothing to decrease). Withdrawn tokens become tokensOwed on the position — they do NOT move to the wallet until you call prepare_uniswap_v3_collect afterwards. This separation matches the on-chain protocol shape and lets the agent batch decrease+collect via rebalance. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
prepare_uniswap_v3_decrease_liquidity accepts 8 parameters: chain, wallet, tokenId, liquidity, deadlineSec, slippageBps, liquidityPct, acknowledgeHighSlippage. 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_decrease_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 VaultPilot MCP. Nothing to install.
prepare_uniswap_v3_decrease_liquidity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prepare_uniswap_v3_decrease_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 prepare_uniswap_v3_decrease_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.
prepare_uniswap_v3_decrease_liquidity 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.