READ-ONLY — report what the server knows about its local config without revealing any secret values. Returns the config-file path + existence, server version, per-chain RPC URL source classification (env-var / provider-key / custom-url / public-fallback), API-key presence + source per service (Et...
AI agents call get_vaultpilot_config_status to retrieve information from VaultPilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_vaultpilot_config_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
READ-ONLY — report what the server knows about its local config without revealing any secret values. Returns the config-file path + existence, server version, per-chain RPC URL source classification (env-var / provider-key / custom-url / public-fallback), API-key presence + source per service (Etherscan, 1inch, Safe, TronGrid, WalletConnect — boolean + source enum, never values), counts of paired Ledger accounts (Solana / TRON), the WC session-topic SUFFIX (last 8 chars only — same convention as get_ledger_status), the agent-side preflight-skill install state, a setupHints array (each entry has a kind discriminator: rate-limit nudges surface when a no-key default RPC has been throttled past threshold and tell the user which provider to sign up for + the wizard subcommand; demo-mode nudges fire on a fresh-install state — no keys, no pairings, no custom RPC — suggesting VAULTPILOT_DEMO=true as the zero-friction first-time path per issue #371), AND a demoMode field that surfaces whether VAULTPILOT_DEMO=true is active plus the activation recipe. Pure local I/O — reads ~/.vaultpilot-mcp/config.json + process.env, no RPC calls, no network. Use this when the user asks 'is my config set up correctly' or 'why is my Solana balance read failing' before suggesting they re-run setup or paste keys. AGENT BEHAVIOR for setupHints: when the array is non-empty, surface each entry's message + recommendation to the user as actionable advice (rate-limit hints also carry providers + setupCommand; demo-mode hints carry just message + recommendation, with the env-var recipe inline in recommendation). Unlike suspectedPoisoning (which is noise), setupHints are real remediation paths the user wants to act on. AGENT BEHAVIOR for demoMode: if the user asks 'how do I try this without a Ledger / API keys' or 'is there a demo mode', read demoMode.howToEnable and relay it verbatim. The same field also carries liveMode: { active, personaId, addresses } reflecting whether set_demo_wallet has been called this session — when liveMode.active is true, signing-class tools have been re-enabled in simulation-only mode (broadcast intercepted with a structured envelope). When the user wants the write-flow walkthrough, call get_demo_wallet to surface the persona list, then set_demo_wallet({ persona: "..." }) to upgrade. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_vaultpilot_config_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.
get_vaultpilot_config_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_vaultpilot_config_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.
Set action: deny in the PolicyLayer policy for get_vaultpilot_config_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.
get_vaultpilot_config_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.