prepare_native_stake_withdraw

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Critical RISK CLASS

Category Financial

Parameters 33 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-native-stake-withdraw.md

WHAT IT DOES

What prepare_native_stake_withdraw does on VaultPilot MCP

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.

RISK

Why prepare_native_stake_withdraw is rated Critical

This tool builds a transaction that moves SOL funds from a stake account back to a wallet, which constitutes a financial operation involving crypto asset movement. While it only prepares an unsigned transaction (reducing direct risk), it is part of a signing flow (Ledger blind-sign) that will ultimately execute a financial transfer of potentially the full SOL balance.

From the tool's definition 'Pulls `amountSol` SOL (or 'max' for the full lamport balance) from an inactive stake account back into the wallet' and 'closes the account and reclaims the rent-exempt seed'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs prepare_native_stake_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_native_stake_withdraw, this is the rule to start with:

prepare_native_stake_withdraw Approval-gated

Any call to prepare_native_stake_withdraw is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "prepare_native_stake_withdraw": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_native_stake_withdraw call is checked against it from then on.

FAQ

Questions about prepare_native_stake_withdraw

What does the prepare_native_stake_withdraw tool do? +

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.

What parameters does prepare_native_stake_withdraw accept? +

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.

How do I enforce a policy on prepare_native_stake_withdraw? +

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.

What risk level is prepare_native_stake_withdraw? +

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.

Can I rate-limit prepare_native_stake_withdraw? +

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.

How do I block prepare_native_stake_withdraw completely? +

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.

What MCP server provides prepare_native_stake_withdraw? +

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.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools → Critical-risk tools on this server →

Across the catalogue

build_redeem_withdraw_tx on Atv →menese_stake on Mcp Menesesdk → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →