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...
AI agents invoke prepare_uniswap_v3_collect 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 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.
prepare_uniswap_v3_collect 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
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 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_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 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_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.