New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_solana_setup_status

READ-ONLY — probe which one-time setup pieces are already in place for a Solana wallet: the durable-nonce account (exists / address / current nonce value / authority) and the set of MarginfiAccount PDAs (index + address). Call this BEFORE planning a multi-step Solana flow (nonce init → MarginFi i...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-solana-setup-status.md

What get_solana_setup_status does on VaultPilot MCP

AI agents call get_solana_setup_status to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
wallet string Yes Solana wallet to probe. Returns the state of the durable-nonce account (exists / address / lamports / currentNonce / authority) and the list of existing Marginf

Parameters from the server's own tool schema.

Why get_solana_setup_status is rated Low

This is a read-only introspection tool that queries blockchain state (Solana account data) to check setup status for nonce accounts and MarginfiAccount PDAs. It performs only data retrieval via getAccountInfo calls with no side effects, no state modification, and no execution of arbitrary operations.

From the tool's definition Tool description explicitly states 'READ-ONLY — probe which one-time setup pieces are already in place' and 'Mirrors the get_ledger_status pattern of cheap chain-read setup introspection.

Questions about get_solana_setup_status

What does the get_solana_setup_status tool do? +

READ-ONLY — probe which one-time setup pieces are already in place for a Solana wallet: the durable-nonce account (exists / address / current nonce value / authority) and the set of MarginfiAccount PDAs (index + address). Call this BEFORE planning a multi-step Solana flow (nonce init → MarginFi init → supply) so agents can skip redundant prepare_* calls instead of re-proposing them and letting the user correct you. Mirrors the get_ledger_status pattern of cheap chain-read setup introspection. One getAccountInfo per probed PDA; no SDK load, no oracle fetch. Returns empty arrays / exists:false when nothing's set up — never throws for an empty wallet. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_solana_setup_status accept? +

get_solana_setup_status accepts 1 parameter: wallet. Required: wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_solana_setup_status? +

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

get_solana_setup_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_solana_setup_status? +

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

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

get_solana_setup_status 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of VaultPilot's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.