Build an unsigned native-stake withdraw tx. Pulls amountSol SOL (or 'max' for the full lamport balance) from an inactive stake account back into the wallet. 'max' closes the account and reclaims the rent-exempt seed; partial-withdraw leaves the account open. Stake MUST be inactive (one full epoch...
AI agents use prepare_native_stake_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 |
|---|---|---|---|
wallet | string | Yes | Solana wallet — must be the stake account's withdrawer authority + receives the SOL. (For stakes created via prepare_native_stake_delegate, wallet === staker == |
amountSol | string | Yes | Human-readable SOL amount to withdraw (e.g. "1.5"), OR the literal string "max" to withdraw the full lamport balance (closes the stake account and reclaims the |
stakeAccount | string | Yes | Base58 stake account address to withdraw from. Stake must be inactive (one full epoch after prepare_native_stake_deactivate). On-chain reverts if the stake is s |
Parameters from the server's own tool schema.
prepare_native_stake_withdraw moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
Build an unsigned native-stake withdraw tx. Pulls amountSol SOL (or 'max' for the full lamport balance) from an inactive stake account back into the wallet. 'max' closes the account and reclaims the rent-exempt seed; partial-withdraw leaves the account open. Stake MUST be inactive (one full epoch after deactivate) — on-chain reverts otherwise; the simulation gate catches it. DURABLE NONCE REQUIRED + same Ledger blind-sign treatment as prepare_native_stake_delegate. 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_native_stake_withdraw accepts 3 parameters: wallet, amountSol, stakeAccount. Required: wallet, amountSol, stakeAccount. 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_native_stake_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_native_stake_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_native_stake_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_native_stake_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_native_stake_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.