get_btc_balances
READ-ONLY — multi-address Bitcoin balance fetch (1-20 addresses). Per-address indexer errors are surfaced as errored entries instead of failing the whole call (mirrors how EVM portfolio enumeration handles flaky RPCs). Each successful entry has the same shape as get_btc_balance's output.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-btc-balances.md
What get_btc_balances does on VaultPilot MCP
AI agents call get_btc_balances 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 |
|---|---|---|---|
addresses | array | Yes | 1-20 Bitcoin addresses to fetch in parallel. Per-address errors are surfaced as `errored` entries rather than failing the whole call. |
Parameters from the server's own tool schema.
Why get_btc_balances is rated Low
This tool only queries and retrieves Bitcoin balance data across 1-20 addresses. It has no side effects, does not execute transactions, does not modify state, and does not create financial obligations.
From the tool's definition Tool name is 'get_btc_balances' and description explicitly states 'READ-ONLY — multi-address Bitcoin balance fetch'. The function retrieves balance information across multiple addresses without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_btc_balances 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_balances, this is the rule to start with:
get_btc_balances 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_balances call is checked against it from then on.
Questions about get_btc_balances
READ-ONLY — multi-address Bitcoin balance fetch (1-20 addresses). Per-address indexer errors are surfaced as errored entries instead of failing the whole call (mirrors how EVM portfolio enumeration handles flaky RPCs). Each successful entry has the same shape as get_btc_balance's output. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_btc_balances accepts 1 parameter: addresses. Required: addresses. 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_balances: 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_balances 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_balances 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_balances. 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_balances 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