prepare_aave_supply
Build an unsigned Aave V3 supply transaction. If an ERC-20 approve() is required first, it is returned as the outer tx and the supply tx is embedded in .next. Both must be signed for the supply to succeed.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-aave-supply.md
What prepare_aave_supply does on VaultPilot MCP
AI agents use prepare_aave_supply 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 | |
approvalCap | string | — | Cap on the ERC-20 approval preceding this action. Omit for "unlimited" (standard DeFi UX — fewer follow-up approvals). Pass "exact" to approve only what this ac |
Parameters from the server's own tool schema.
Why prepare_aave_supply is rated Critical
This tool prepares transactions to supply assets into Aave V3, a DeFi lending protocol. Supplying assets commits funds to an external financial protocol (DeFi), and also requires an ERC-20 approve() which grants token spending allowances. This constitutes a financial commitment of crypto assets, placing it in the Financial category.
From the tool's definition Build an unsigned Aave V3 supply transaction... Both must be signed for the supply to succeed
Attacks that exploit this kind of access
The rule that runs prepare_aave_supply 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_supply, this is the rule to start with:
Any call to prepare_aave_supply 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_supply call is checked against it from then on.
Questions about prepare_aave_supply
Build an unsigned Aave V3 supply transaction. If an ERC-20 approve() is required first, it is returned as the outer tx and the supply tx is embedded in .next. Both must be signed for the supply to succeed. 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_supply accepts 5 parameters: asset, chain, amount, wallet, approvalCap. 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_supply: 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_supply 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_supply 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_supply. 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_supply 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