pair_ledger_btc

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

High RISK CLASS

Category Execute

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/pair-ledger-btc.md

WHAT IT DOES

What pair_ledger_btc does on VaultPilot MCP

AI agents invoke pair_ledger_btc 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
`gapLimit`	integer	—	BIP44 gap limit — stop walking each (type, chain) after this many consecutive addresses with zero on-chain history. Default 20 (matches Electrum / Sparrow / Tre
`accountIndex`	integer	—	Ledger Bitcoin account slot. One call enumerates ALL FOUR address types for the given index (legacy at `44'/0'/<n>'/...`, p2sh-segwit at `49'/0'/<n>'/...`, nati

Parameters from the server's own tool schema.

RISK

Why pair_ledger_btc is rated High

This tool establishes a USB HID connection to a physical Ledger hardware wallet and enumerates cryptographic key paths/addresses across multiple derivation paths. It triggers an external hardware operation (USB device enumeration and communication), which goes beyond a simple read.

From the tool's definition 'Pair the host's directly-connected Ledger device for Bitcoin signing' via 'USB HID via @ledgerhq/hw-app-btc' — enumerates all four address types by communicating with a physical hardware device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pair_ledger_btc 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 pair_ledger_btc, this is the rule to start with:

pair_ledger_btc Rate-limited

pair_ledger_btc stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pair_ledger_btc": {
      "limits": [
        {
          "counter": "pair_ledger_btc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every pair_ledger_btc call is checked against it from then on.

FAQ

Questions about pair_ledger_btc

What does the pair_ledger_btc tool do? +

Pair the host's directly-connected Ledger device for Bitcoin signing. REQUIREMENTS: Ledger plugged in over USB, device unlocked, the 'Bitcoin' app open on-screen. Ledger Live's WalletConnect relay does NOT expose bip122 accounts to dApps, so Bitcoin signing goes over USB HID via @ledgerhq/hw-app-btc (same USB path as Solana / TRON). ONE CALL ENUMERATES ALL FOUR ADDRESS TYPES for the requested accountIndex (default 0): legacy P2PKH (44'/0'/<n>'/0/0 → 1...), P2SH-wrapped segwit (49'/0'/<n>'/0/0 → 3...), native segwit P2WPKH (84'/0'/<n>'/0/0 → bc1q...), and taproot P2TR (86'/0'/<n>'/0/0 → bc1p...). All four are cached so get_ledger_status can report them under the bitcoin: [...] section. Call again with a different accountIndex to expose additional accounts. Read-only on the device — the Ledger BTC app does not prompt during getWalletPublicKey by default. Phase 1 is mainnet-only. 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.

What parameters does pair_ledger_btc accept? +

pair_ledger_btc accepts 2 parameters: gapLimit, accountIndex. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pair_ledger_btc? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for pair_ledger_btc: 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.

What risk level is pair_ledger_btc? +

pair_ledger_btc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pair_ledger_btc? +

Yes. Add a rate_limit block to the pair_ledger_btc 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.

How do I block pair_ledger_btc completely? +

Set action: deny in the PolicyLayer policy for pair_ledger_btc. 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.

What MCP server provides pair_ledger_btc? +

pair_ledger_btc 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.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →