build_withdraw_tx

Build the transaction steps required to withdraw vault shares from an ATV vault and receive an output token.

SERVERAtv SOURCEaarna-ai/atv
Critical RISK CLASS
Category Financial
Parameters 60 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aarna-ai-atv/build-withdraw-tx.md

What build_withdraw_tx does on Atv

AI agents use build_withdraw_tx to commit financial operations through Atv, usually the final step of a payment, billing, or trading workflow. A call moves real money.

ParameterTypeRequiredDescription
simulate string Pass 'true' to include a gas estimate in the response
slippage string Slippage tolerance as a percentage, e.g. '0.5'
userAddress string EVM address of the withdrawer
vaultAddress string Vault contract address
oTokenAddress string Output token address to receive
sharesToWithdraw string Human-readable share amount to withdraw, e.g. '100'

Parameters from the server's own tool schema.

Why build_withdraw_tx is rated Critical

This tool constructs transactions that move financial assets (vault shares) out of yield vaults and convert them to output tokens on Ethereum/Base. Withdrawing vault shares is a financial operation that commits to moving funds. Combined with the server context of 'tokenized yield vaults' and sibling tools like build_deposit_tx and build_stake_tx, this clearly falls in the Financial category.

From the tool's definition "Build the transaction steps required to withdraw vault shares from an ATV vault and receive an output token"

Questions about build_withdraw_tx

What does the build_withdraw_tx tool do? +

Build the transaction steps required to withdraw vault shares from an ATV vault and receive an output token. 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.

What parameters does build_withdraw_tx accept? +

build_withdraw_tx accepts 6 parameters: simulate, slippage, userAddress, vaultAddress, oTokenAddress, sharesToWithdraw. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on build_withdraw_tx? +

Register the Atv MCP server in PolicyLayer and add a rule for build_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.

What risk level is build_withdraw_tx? +

build_withdraw_tx is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit build_withdraw_tx? +

Yes. Add a rate_limit block to the build_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.

How do I block build_withdraw_tx completely? +

Set action: deny in the PolicyLayer policy for build_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.

What MCP server provides build_withdraw_tx? +

build_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Atv's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.