Pair the host's directly-connected Ledger device for Litecoin signing. REQUIREMENTS: Ledger plugged in over USB, device unlocked, the 'Litecoin' app open on-screen. Ledger Live's WalletConnect relay does not expose Litecoin accounts to dApps, so signing goes over USB HID via @ledgerhq/hw-app-btc ...
AI agents call pair_ledger_ltc to retrieve information from VaultPilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
gapLimit | integer | — | BIP44 gap limit — stop walking each (type, chain) after this many consecutive addresses with zero on-chain history. Default 20. |
accountIndex | integer | — | Ledger Litecoin account slot. One call enumerates ALL FOUR address types (legacy at `44'/2'/<n>'/...`, p2sh-segwit at `49'/2'/<n>'/...`, native segwit at `84'/2 |
Parameters from the server's own tool schema.
Even though pair_ledger_ltc only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Pair the host's directly-connected Ledger device for Litecoin signing. REQUIREMENTS: Ledger plugged in over USB, device unlocked, the 'Litecoin' app open on-screen. Ledger Live's WalletConnect relay does not expose Litecoin accounts to dApps, so signing goes over USB HID via @ledgerhq/hw-app-btc (the same SDK as Bitcoin, with currency:'litecoin' selecting Litecoin-specific encoding). One call enumerates the four BIP-44 address types (legacy L…, p2sh-segwit M…, native segwit ltc1q…, taproot ltc1p…) for the given account index. BIP-44 coin_type 2. Per-type fault-tolerant: each address-type walk runs independently, so one type's failure (e.g. the Ledger Litecoin app currently rejects bech32m/taproot with 'Unsupported address format bech32m') does NOT abort the others — the failed type is recorded under skipped[] in the response and the remaining three are paired and persisted. Note: Litecoin Core has not activated Taproot on mainnet, so ltc1p… outputs would not be spendable anyway — taproot pairing is effectively forward-compat only. All paired entries surface under the litecoin: [...] section of get_ledger_status. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
pair_ledger_ltc accepts 2 parameters: gapLimit, 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 pair_ledger_ltc: 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.
pair_ledger_ltc 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 pair_ledger_ltc 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 pair_ledger_ltc. 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.
pair_ledger_ltc 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.