get_demo_wallet

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 00 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-demo-wallet.md

WHAT IT DOES

What get_demo_wallet does on VaultPilot MCP

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

RISK

Why get_demo_wallet is rated Low

This tool retrieves and queries the current demo wallet configuration and available personas without modifying state, executing code, deleting data, or moving funds. It is purely informational—enabling the agent to understand the current wallet context before taking action. While it operates in a crypto/DeFi context, the tool itself performs no financial transactions or irreversible operations.

From the tool's definition Tool reports wallet state, enumerates available personas and addresses, and returns configuration status. Keywords: 'Report', 'confirm', 'enumerates', 'RESPONSE' shows read-only JSON output with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_demo_wallet Allowed

get_demo_wallet 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": {
    "get_demo_wallet": {}
  }
}

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

FAQ

Questions about get_demo_wallet

What does the get_demo_wallet tool do? +

Report the active demo wallet (live mode), confirm default demo mode (no wallet set), or report why demo mode isn't active when the env var is missing or misconfigured. ALWAYS enumerates the available personas + their addresses + descriptions regardless of VAULTPILOT_DEMO state, so the agent can offer the user a choice without hardcoding the list (issue #392). RESPONSE: { demoActive, mode, envState: 'enabled' | 'unset' | 'invalid', personas, matrix, [active], [message] }. When envState is 'unset' or 'invalid' the message field tells the user how to fix it (set VAULTPILOT_DEMO=true exact literal, lowercase). When envState is 'enabled', active carries the current live wallet (or null in default demo mode). MATRIX (issue #409 enrichment): each cell in matrix[chain][type] carries a rehearsableFlows: string[] field listing multi-step / state-dependent demo flows the cell's existing on-chain state already supports end-to-end (e.g. aave_supply, marinade_stake, swap_eth_usdc), and an optional flowGaps field listing flows the persona archetype implies but the wallet's current state does NOT support, with a one-line recommendation (switch persona / exit demo / pair Ledger). Read these BEFORE the user picks a flow so you offer rehearsable flows up-front and steer them off flows that would loop on missing on-chain state (the simulated send returned in demo mode never mutates state, so any flow whose precondition is itself a state change can't be rehearsed end-to-end against a wallet that doesn't already have it). It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_demo_wallet? +

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

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

Can I rate-limit get_demo_wallet? +

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

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

get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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