rescan_ltc_account
READ-ONLY — refresh the cached on-chain txCount for every paired Litecoin 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 inde...
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/rescan-ltc-account.md
What rescan_ltc_account does on VaultPilot MCP
AI agents call rescan_ltc_account 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 |
|---|---|---|---|
accountIndex | integer | Yes | Ledger Litecoin account slot to rescan. Must already be paired (call `pair_ledger_ltc` first). Re-queries the indexer for the live `txCount` of every cached add |
Parameters from the server's own tool schema.
Why rescan_ltc_account is rated Low
The tool explicitly declares itself READ-ONLY and performs no financial transactions or irreversible actions. It re-queries an indexer to refresh cached transaction counts for Litecoin addresses. While it does update a persisted local cache (which edges toward Write), the primary action is data retrieval from an external indexer, and the cache update is a side effect of reading.
From the tool's definition READ-ONLY — refresh the cached on-chain `txCount` for every paired Litecoin address under one Ledger account by re-querying the indexer. Pure indexer-side: NO Ledger / USB interaction.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs rescan_ltc_account 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 rescan_ltc_account, this is the rule to start with:
rescan_ltc_account 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 rescan_ltc_account call is checked against it from then on.
Questions about rescan_ltc_account
READ-ONLY — refresh the cached on-chain txCount for every paired Litecoin 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_ltc scan time. Updates the persisted cache, so subsequent get_ltc_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_ltc to extend the walked window); unverifiedChains: [...] (tail probe REJECTED for that chain — indeterminate, usually a transient indexer hiccup, re-run rescan_ltc_account rather than re-pairing); neither field present → all walked chains confirmed healthy. Indexer fan-out is bounded to LITECOIN_INDEXER_PARALLELISM concurrent requests (default 8) to stay under litecoinspace.org's free-tier rate limits; transient 429s and network errors are retried once internally. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
rescan_ltc_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_ltc_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_ltc_account 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 rescan_ltc_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_ltc_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_ltc_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.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue