exit_demo_mode

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 40 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/exit-demo-mode.md

WHAT IT DOES

What exit_demo_mode does on VaultPilot MCP

AI agents call exit_demo_mode 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.

Parameter	Type	Required	Description
`chains`	array	—	Chains the user intends to use. Drives which RPC / API keys to recommend. Defaults to ['ethereum'] when omitted.
`hasLedger`	boolean	—	Whether the user confirmed they have a Ledger device. Pass `false` to get a deferral message recommending they stay in demo until they have hardware. Omit if un
`acquireKeys`	boolean	—	Whether the user wants help acquiring API keys. Affects recommendation tone — true expands signup links, false keeps the response short.
`hasRunSetup`	boolean	—	Whether the user has previously run `vaultpilot-mcp-setup`. When true, the response skips the setup-wizard walkthrough.

Parameters from the server's own tool schema.

RISK

Why exit_demo_mode is rated Low

The tool explicitly states it is stateless and read-only, producing only a step-by-step guide/decision tree for the user. It cannot change any state, unset environment variables, or trigger any real-world actions. It is purely informational output, making it a Read category tool with low severity.

From the tool's definition Stateless / read-only — calling it does NOT change demo state. This tool produces a tailored decision tree the agent walks the user through. The MCP server CANNOT actually unset VAULTPILOT_DEMO or invoke the setup wizard.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

exit_demo_mode Allowed

exit_demo_mode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "exit_demo_mode": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about exit_demo_mode

What does the exit_demo_mode tool do? +

Build a step-by-step guide for the user to exit demo mode and switch to operational (real signing) mode. The MCP server CANNOT actually unset VAULTPILOT_DEMO or invoke the setup wizard — both require user action outside the MCP. This tool produces a tailored decision tree the agent walks the user through. Stateless / read-only — calling it does NOT change demo state. AGENT BEHAVIOR — call this tool ONLY after explicitly confirming with the user that they want to leave demo mode (e.g., 'I'm ready to set this up for real', 'I have my Ledger now', 'exit demo'). DO NOT call it as a probe — the response is verbose and presumes intent. Before calling, ASK the user: (1) do you have a Ledger device? (2) have you already run vaultpilot-mcp-setup? (3) which chains do you intend to use? Pass the answers as args so the response is tailored. If hasLedger=false, the response recommends DEFERRING the exit (without a Ledger, operational mode gives no functionality demo doesn't already have). Surface that verbatim. Outside demo mode, the tool returns a no-op response indicating there's nothing to exit. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does exit_demo_mode accept? +

exit_demo_mode accepts 4 parameters: chains, hasLedger, acquireKeys, hasRunSetup. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on exit_demo_mode? +

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

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

Can I rate-limit exit_demo_mode? +

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

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

exit_demo_mode 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →