prepare_native_stake_deactivate

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

High RISK CLASS

Category Execute

Parameters 22 required

Recommended Rate-limitedsee 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-deactivate.md

WHAT IT DOES

What prepare_native_stake_deactivate does on VaultPilot MCP

AI agents invoke prepare_native_stake_deactivate to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`wallet`	string	Yes	Solana wallet — must be the stake account's staker authority (the wallet that originally created the stake).
`stakeAccount`	string	Yes	Base58 stake account address to deactivate. Discovery: call get_solana_staking_positions; the wallet's native stake accounts are listed under `native[].stakePub

Parameters from the server's own tool schema.

RISK

Why prepare_native_stake_deactivate is rated High

This tool constructs a signed or signable transaction that modifies stake account state on-chain. Although deactivation is technically reversible if caught during the cooldown period, in practice it locks funds from rewards for 2-3 days and initiates a one-way state machine toward withdrawal.

From the tool's definition Tool builds an unsigned transaction that initiates a blockchain state change ('initiates the one-epoch cooldown after which the stake becomes withdrawable'). It operates on Solana's stake program, modifying stake account status irreversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

prepare_native_stake_deactivate Rate-limited

prepare_native_stake_deactivate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "prepare_native_stake_deactivate": {
      "limits": [
        {
          "counter": "prepare_native_stake_deactivate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_deactivate call is checked against it from then on.

FAQ

Questions about prepare_native_stake_deactivate

What does the prepare_native_stake_deactivate tool do? +

Build an unsigned native-stake deactivate tx. Initiates the one-epoch (~2-3 days) cooldown after which the stake becomes withdrawable; the stake earns no rewards during deactivation. Wallet must be the stake account's staker authority. After the cooldown lapses, run prepare_native_stake_withdraw to drain the account (or partial-withdraw to leave it open). DURABLE NONCE REQUIRED + same Ledger blind-sign treatment as prepare_native_stake_delegate. The on-chain stake program reverts if the stake is already deactivating/inactive — the simulation gate catches it. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does prepare_native_stake_deactivate accept? +

prepare_native_stake_deactivate accepts 2 parameters: wallet, stakeAccount. Required: wallet, 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_deactivate? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_native_stake_deactivate: 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_deactivate? +

prepare_native_stake_deactivate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit prepare_native_stake_deactivate? +

Yes. Add a rate_limit block to the prepare_native_stake_deactivate 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_deactivate completely? +

Set action: deny in the PolicyLayer policy for prepare_native_stake_deactivate. 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_deactivate? +

prepare_native_stake_deactivate 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 → High-risk tools on this server →

Across the catalogue

hook_native_function on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →