This record as markdown: /tools/aarna-ai-atv/build-deposit-tx.md
What build_deposit_tx does on Atv
AI agents invoke build_deposit_tx to trigger actions in Atv. 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 |
|---|---|---|---|
userAddress | string | — | EVM address of the depositor |
vaultAddress | string | — | Vault contract address |
depositAmount | string | — | Human-readable deposit amount, e.g. '100' for 100 USDC |
depositTokenAddress | string | — | ERC20 token address to deposit |
Parameters from the server's own tool schema.
Why build_deposit_tx is rated High
This tool builds and prepares blockchain transactions (token approval + deposit) for execution. While it 'builds' rather than directly submits, it constructs executable transaction payloads that move user tokens into a vault. The action involves transferring asset ownership into a vault smart contract, which is a financial-adjacent operation.
From the tool's definition Build the transaction steps required to deposit tokens into an ATV vault. Returns an ordered array of transactions (approve then deposit) that must be sent in order.
Attacks that exploit this kind of access
The rule that runs build_deposit_tx safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Atv, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_deposit_tx, this is the rule to start with:
build_deposit_tx stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Atv, apply this rule, and every build_deposit_tx call is checked against it from then on.
Questions about build_deposit_tx
Build the transaction steps required to deposit tokens into an ATV vault. Returns an ordered array of transactions (approve then deposit) that must be sent in order. It is categorised as a Execute tool in the Atv MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_deposit_tx accepts 4 parameters: userAddress, vaultAddress, depositAmount, depositTokenAddress. The full parameter table on this page comes from the server's own tool schema.
Register the Atv MCP server in PolicyLayer and add a rule for build_deposit_tx: 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 Atv. Nothing to install.
build_deposit_tx 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 build_deposit_tx 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_deposit_tx. 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_deposit_tx is provided by the Atv MCP server (aarna-ai/atv). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Atv, and thousands of servers like it.
This server
Across the catalogue