get_btc_balance
READ-ONLY — fetch the confirmed + mempool balance for a single Bitcoin mainnet address. Returns sats (raw) and BTC (formatted), separated into confirmed and mempool components, plus the address type (legacy / P2SH / native segwit / taproot) and a tx count. Backed by mempool.space's public API by ...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-balance.md
What get_btc_balance does on VaultPilot MCP
AI agents call get_btc_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 |
|---|---|---|---|
address | string | Yes | Bitcoin mainnet address. Accepts legacy (1...), P2SH (3...), native segwit (bc1q...), and taproot (bc1p...). Testnet/signet not supported. |
Parameters from the server's own tool schema.
Why get_btc_balance is rated Low
This tool performs a read-only query of blockchain data (Bitcoin address balance) using a public indexer API. It returns informational data only (sats, BTC balance, address type, transaction count) without creating, modifying, deleting, executing code, or committing financial transactions.
From the tool's definition Tool name is 'get_btc_balance' and description explicitly states 'READ-ONLY — fetch the confirmed + mempool balance for a single Bitcoin mainnet address.' It retrieves balance information with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs get_btc_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_balance, this is the rule to start with:
get_btc_balance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_btc_balance call is checked against it from then on.
Questions about get_btc_balance
READ-ONLY — fetch the confirmed + mempool balance for a single Bitcoin mainnet address. Returns sats (raw) and BTC (formatted), separated into confirmed and mempool components, plus the address type (legacy / P2SH / native segwit / taproot) and a tx count. Backed by mempool.space's public API by default; configurable via BITCOIN_INDEXER_URL env var or userConfig.bitcoinIndexerUrl for self-hosted Esplora / Electrs. Phase 1 is mainnet-only (testnet/signet rejected). It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_btc_balance accepts 1 parameter: address. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_btc_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.
get_btc_balance 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_btc_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.
Set action: deny in the PolicyLayer policy for get_btc_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.
get_btc_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.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue