This record as markdown: /tools/aarna-ai-atv/build-redeem-withdraw-tx.md
What build_redeem_withdraw_tx does on Atv
AI agents use build_redeem_withdraw_tx to commit financial operations through Atv, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
oTokens | string | — | Human-readable amount of output tokens to redeem |
userAddress | string | — | EVM address of the withdrawer |
batchCounter | string | — | Batch identifier from the queue contract for this withdrawal |
vaultAddress | string | — | Vault contract address |
Parameters from the server's own tool schema.
Why build_redeem_withdraw_tx is rated Critical
This tool builds a transaction to redeem/claim funds from a tokenized yield vault. Redeeming a withdrawal moves assets (tokens/funds) from the vault back to the user's wallet, which constitutes a financial operation involving the movement of real on-chain assets on Ethereum or Base. Misuse could result in unauthorized redemption of vault assets or loss of funds, warranting critical severity.
From the tool's definition "Build the transaction step to claim (redeem) a completed queued withdrawal from an ATV vault"
Attacks that exploit this kind of access
The rule that runs build_redeem_withdraw_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_redeem_withdraw_tx, this is the rule to start with:
Any call to build_redeem_withdraw_tx is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Atv, apply this rule, and every build_redeem_withdraw_tx call is checked against it from then on.
Questions about build_redeem_withdraw_tx
Build the transaction step to claim (redeem) a completed queued withdrawal from an ATV vault. It is categorised as a Financial tool in the Atv MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
build_redeem_withdraw_tx accepts 4 parameters: oTokens, userAddress, batchCounter, vaultAddress. 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_redeem_withdraw_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_redeem_withdraw_tx 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_redeem_withdraw_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_redeem_withdraw_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_redeem_withdraw_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.
Across the catalogue