prepare_solana_nonce_init
Explicit one-time setup of a per-wallet durable-nonce account at the deterministic PDA PublicKey.createWithSeed(wallet, 'vaultpilot-nonce-v1', SystemProgram.programId). MOST USERS DO NOT NEED TO CALL THIS DIRECTLY — prepare_solana_native_send / prepare_solana_spl_send auto-bundle the same setup i...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-solana-nonce-init.md
What prepare_solana_nonce_init does on VaultPilot MCP
AI agents invoke prepare_solana_nonce_init 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 that will own (and authorize) the durable-nonce account. The nonce account address is derived deterministically via PublicKey.createWithSeed(walle |
Parameters from the server's own tool schema.
Why prepare_solana_nonce_init is rated High
This tool triggers an on-chain operation that initializes a durable-nonce account on Solana, consuming SOL for rent-exemption. It is an Execute-class action because it runs an external blockchain transaction with real effects (account creation, SOL expenditure).
From the tool's definition 'Explicit one-time setup of a per-wallet durable-nonce account', 'Costs ~0.00144 SOL rent-exempt seed + ~0.000005 SOL'
Attacks that exploit this kind of access
The rule that runs prepare_solana_nonce_init 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_solana_nonce_init, this is the rule to start with:
prepare_solana_nonce_init 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.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_solana_nonce_init call is checked against it from then on.
Questions about prepare_solana_nonce_init
Explicit one-time setup of a per-wallet durable-nonce account at the deterministic PDA PublicKey.createWithSeed(wallet, 'vaultpilot-nonce-v1', SystemProgram.programId). MOST USERS DO NOT NEED TO CALL THIS DIRECTLY — prepare_solana_native_send / prepare_solana_spl_send auto-bundle the same setup into the user's first send. Use this tool when the user wants the setup standalone (e.g. before a Jupiter swap or MarginFi action, which can't safely auto-bundle due to size + ALT constraints), or to re-init after a prepare_solana_nonce_close. Costs ~0.00144 SOL rent-exempt seed + ~0.000005 SOL tx fee; the rent is fully reclaimable via prepare_solana_nonce_close. Refuses if a nonce account already exists at the derived PDA. This init tx uses a regular recent blockhash (no nonce to use yet — same constraint that makes auto-bundling possible inside native/SPL sends). 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.
prepare_solana_nonce_init accepts 1 parameter: wallet. Required: 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_solana_nonce_init: 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_solana_nonce_init is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prepare_solana_nonce_init 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_solana_nonce_init. 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_solana_nonce_init 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