set_demo_wallet

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 40 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/set-demo-wallet.md

WHAT IT DOES

What set_demo_wallet does on VaultPilot MCP

AI agents use set_demo_wallet to create or update resources in VaultPilot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultPilot MCP environment.

Parameter	Type	Required	Description
`type`	string	—	Type / archetype dimension of the demo-wallet matrix. Pair with `chain` to load a single (chain, type) cell.
`chain`	string	—	Chain dimension of the demo-wallet matrix. Pair with `type` to load a single (chain, type) cell. Replaces any previous slot for this chain; other chains stay as
`custom`	object	—	Custom address bundle. Mutually exclusive with `chain`+`type` and `persona`. At least one chain field must be non-empty.
`persona`	string	—	Persona / type ID to batch-activate across every chain that has a curated cell. Convenience over four `{ chain, type }` calls. Mutually exclusive with `chain`+`

Parameters from the server's own tool schema.

RISK

Why set_demo_wallet is rated Medium

This tool modifies the active session state by switching which demo wallet is in use, and notably 'upgrades' the operational mode so that certain tools run against real on-chain state. It is a Write action (changing configuration/state reversibly), not Destructive or Financial on its own.

From the tool's definition switch the active demo wallet...demo mode upgrades from default...to live mode (prepare_*, simulate_*, preview_send run REAL against the wallet's on-chain state)

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_demo_wallet Rate-limited

set_demo_wallet stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_demo_wallet": {
      "limits": [
        {
          "counter": "set_demo_wallet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about set_demo_wallet

What does the set_demo_wallet tool do? +

DEMO MODE ONLY — switch the active demo wallet via one of three input shapes. Once a wallet is set, demo mode upgrades from default (signing-class tools refuse) to live mode (prepare_*, simulate_*, preview_send run REAL against the wallet's on-chain state; send_transaction returns a simulation envelope instead of broadcasting). INPUT SHAPES: (1) { chain, type } — per-cell loader. e.g. { chain: 'bitcoin', type: 'whale' } loads ONE address into the BTC slot, leaving evm/solana/tron slots untouched. Multiple per-cell calls accumulate; same chain twice replaces. Chains: evm | solana | tron | bitcoin. Types: defi-degen | stable-saver | staking-maxi | whale. Some cells are intentionally null (BTC defi-degen, Solana staking-maxi, etc.) — call get_demo_wallet first to see the matrix. (2) { persona } — batch loader. Same as four per-cell calls for one type at once. Convenience for 'load me a whole whale wallet across every chain that has one'. (3) { custom: { evm: [...], solana: [...], tron: [...], bitcoin: [...] } } — arbitrary addresses (read-only, no security risk). Pass {} (no args) to clear and return to default demo mode. Calling outside demo mode (env unset) returns a no-op response — the tool stays available so an agent can always discover the surface, but never affects real signing. It is categorised as a Write tool in the VaultPilot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does set_demo_wallet accept? +

set_demo_wallet accepts 4 parameters: type, chain, custom, persona. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_demo_wallet? +

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

set_demo_wallet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_demo_wallet? +

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

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

set_demo_wallet 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →