get_btc_multisig_balance

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 21 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-btc-multisig-balance.md

WHAT IT DOES

What get_btc_multisig_balance does on VaultPilot MCP

AI agents call get_btc_multisig_balance 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
`gapLimit`	integer	—	BIP-44 gap limit — stop walking each chain after N consecutive empty addresses. Default 20 (matches Sparrow / Specter / BIP-44 recommendation). Cap of 100 to bo
`walletName`	string	Yes	Name of a registered multi-sig wallet (matches the `name` passed to `register_btc_multisig_wallet`).

Parameters from the server's own tool schema.

RISK

Why get_btc_multisig_balance is rated Low

The tool is purely a read/query operation: it derives addresses locally from stored xpubs, queries an Esplora indexer for balances, and returns aggregated balance data. There are no writes, executions, or financial transactions involved. 'Watch-only' and 'No device touch' confirm no side effects. Severity is low because misuse only exposes balance information, not private keys or funds.

From the tool's definition Watch-only balance read for a registered multi-sig wallet... No device touch — addresses are derived locally from the stored cosigner xpubs...

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_btc_multisig_balance Allowed

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

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

FAQ

Questions about get_btc_multisig_balance

What does the get_btc_multisig_balance tool do? +

Watch-only balance read for a registered multi-sig wallet. Walks both BIP-32 chains (chain=0 receive, chain=1 change) up to a gap-limit window (default 20, BIP-44 standard), queries each derived address via the configured Esplora indexer, returns the aggregate balance plus per-address breakdown for entries with on-chain history. No device touch — addresses are derived locally from the stored cosigner xpubs. Phase 3 supports P2WSH (wsh) wallets only; taproot lands in a follow-up PR. 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_btc_multisig_balance accept? +

get_btc_multisig_balance accepts 2 parameters: gapLimit, walletName. Required: walletName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_btc_multisig_balance? +

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

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

Can I rate-limit get_btc_multisig_balance? +

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

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

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