prepare_aave_withdraw
Build an unsigned Aave V3 withdraw transaction. Pass amount: "max" to withdraw the entire aToken balance.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-aave-withdraw.md
What prepare_aave_withdraw does on VaultPilot MCP
AI agents use prepare_aave_withdraw to commit financial operations through VaultPilot MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
asset | string | Yes | |
chain | string | — | |
amount | string | Yes | Human-readable decimal amount of `asset`, NOT raw wei/base units. Example: "1.5" for 1.5 USDC, "0.01" for 0.01 ETH. Pass "max" for full-balance withdraw/repay. |
wallet | string | Yes |
Parameters from the server's own tool schema.
Why prepare_aave_withdraw is rated Critical
This tool constructs a DeFi withdrawal transaction on Aave V3, which moves crypto assets (aTokens redeemed for underlying assets) out of a lending protocol. Even though it only builds an unsigned transaction, it is a direct precursor to a financial operation that transfers crypto holdings.
From the tool's definition 'Build an unsigned Aave V3 withdraw transaction' and 'withdraw the entire aToken balance'
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs prepare_aave_withdraw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_aave_withdraw, this is the rule to start with:
Any call to prepare_aave_withdraw is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_aave_withdraw call is checked against it from then on.
Questions about prepare_aave_withdraw
Build an unsigned Aave V3 withdraw transaction. Pass amount: "max" to withdraw the entire aToken balance. It is categorised as a Financial tool in the VaultPilot MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
prepare_aave_withdraw accepts 4 parameters: asset, chain, amount, wallet. Required: asset, amount, wallet. 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_aave_withdraw: 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_aave_withdraw 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 prepare_aave_withdraw 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_aave_withdraw. 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_aave_withdraw 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.
More on VaultPilot, and thousands of servers like it.
Across the catalogue