AI agents use build_lp_deposit to commit financial operations through Agent — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
vault | string | Yes | Known any-token LP vault address. |
chainId | integer | Yes | EVM chain id (mainnet = 1 in v1). |
amountIn | string | Yes | Amount in base units (integer string, e.g. USDC 6dp). |
recipient | string | Yes | Recipient / payer address (the wallet that signs + receives). |
inputToken | string | Yes | Any held token to deposit. |
slippageBps | integer | — | Optional slippage budget in basis points (0–10000). |
Parameters from the server's own tool schema.
Although the tool only builds the transaction and does not broadcast it, the resulting artifact is a financial operation that moves user tokens into a liquidity pool. The 'approve → Permit2 sign → router.depositAnyToken' pipeline represents a multi-step financial commitment. If an AI agent were to hand these transactions to a signing mechanism, it would result in real asset movement.
From the tool's definition 'LP deposit plan (approve → Permit2 sign → router.depositAnyToken)' — builds a transaction sequence committing user funds into a liquidity pool, a financial obligation involving token transfers and DeFi protocol interaction.
Attacks that exploit this kind of access
Build a NON-CUSTODIAL any-token LP deposit plan (approve → Permit2 sign → router.depositAnyToken) for the caller to sign + broadcast. No broadcast. It is categorised as a Financial tool in the Agent MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
build_lp_deposit accepts 6 parameters: vault, chainId, amountIn, recipient, inputToken, slippageBps. Required: vault, chainId, amountIn, recipient, inputToken. The full parameter table on this page comes from the server's own tool schema.
Register the Agent MCP server in PolicyLayer and add a rule for build_lp_deposit: 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 Agent. Nothing to install.
build_lp_deposit 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 build_lp_deposit 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 build_lp_deposit. 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.
build_lp_deposit is provided by the Agent MCP server (https://fluxiq.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
build_lp_deposit is one line of Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →