prepare_uniswap_v3_collect
Build an unsigned Uniswap V3 LP collect transaction — harvests every token the position is owed (decreased liquidity from prior prepare_uniswap_v3_decrease_liquidity calls + accrued swap fees) up to uint128.max per side. Hard-refuses when the tokenId is not owned by wallet. The protocol auto-sett...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-uniswap-v3-collect.md
What prepare_uniswap_v3_collect does on VaultPilot MCP
AI agents use prepare_uniswap_v3_collect to commit financial operations through VaultPilot MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | — | |
wallet | string | Yes | |
tokenId | string | Yes | ERC-721 tokenId of the LP NFT to harvest fees + tokensOwed from. Must be owned by `wallet`. |
recipient | string | — | Address to receive the harvested tokens. Default: wallet (the position owner). |
Parameters from the server's own tool schema.
Why prepare_uniswap_v3_collect is rated Critical
This tool builds a transaction that collects/harvests crypto tokens (fees and liquidity) from a Uniswap V3 LP position and transfers them to a recipient address. While it produces an unsigned transaction (requiring a subsequent signing step), it initiates a financial operation that moves crypto assets — potentially large amounts up to uint128.max — and allows redirecting funds to an arbitrary recipient address,…
From the tool's definition harvests every token the position is owed...accrued swap fees...up to uint128.max per side...pass an address to send the harvest elsewhere
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs prepare_uniswap_v3_collect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_uniswap_v3_collect, this is the rule to start with:
Any call to prepare_uniswap_v3_collect is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_uniswap_v3_collect call is checked against it from then on.
Questions about prepare_uniswap_v3_collect
Build an unsigned Uniswap V3 LP collect transaction — harvests every token the position is owed (decreased liquidity from prior prepare_uniswap_v3_decrease_liquidity calls + accrued swap fees) up to uint128.max per side. Hard-refuses when the tokenId is not owned by wallet. The protocol auto-settles uncollected fee growth into tokensOwed inside the call, so even a position with tokensOwed{0,1}=0 may receive tokens. recipient defaults to the wallet; pass an address to send the harvest elsewhere. It is categorised as a Financial tool in the VaultPilot MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
prepare_uniswap_v3_collect accepts 4 parameters: chain, wallet, tokenId, recipient. 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_collect: 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_collect is a Financial 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_collect 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_collect. 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_collect 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.
Across the catalogue