READ-ONLY — refresh the cached on-chain txCount for every paired Bitcoin address under one Ledger account by re-querying the indexer. Pure indexer-side: NO Ledger / USB interaction. Use this after the user has received funds (so a previously-empty cached address now has history) or when the index...
AI agents invoke rescan_btc_account to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
accountIndex | integer | Yes | Ledger Bitcoin account slot to rescan. Must already be paired (call `pair_ledger_btc` first). Re-queries the indexer for the live `txCount` of every cached addr |
Parameters from the server's own tool schema.
rescan_btc_account triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
READ-ONLY — refresh the cached on-chain txCount for every paired Bitcoin address under one Ledger account by re-querying the indexer. Pure indexer-side: NO Ledger / USB interaction. Use this after the user has received funds (so a previously-empty cached address now has history) or when the indexer was stale at the original pair_ledger_btc scan time. Updates the persisted cache, so subsequent get_btc_account_balance reflects the refresh without another rescan. Three-state extend signal: needsExtend: true (trailing buffer address on any cached chain has on-chain history — re-run pair_ledger_btc to extend the walked window); unverifiedChains: [...] (tail probe REJECTED for that chain — indeterminate, usually a transient indexer hiccup, re-run rescan_btc_account rather than re-pairing); neither field present → all walked chains confirmed healthy. Indexer fan-out is bounded to BITCOIN_INDEXER_PARALLELISM concurrent requests (default 8) to stay under mempool.space's free-tier rate limits; transient 429s and network errors are retried once internally. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
rescan_btc_account accepts 1 parameter: accountIndex. Required: accountIndex. 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 rescan_btc_account: 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.
rescan_btc_account is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rescan_btc_account 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 rescan_btc_account. 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.
rescan_btc_account 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.