sign_btc_multisig_psbt

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/sign-btc-multisig-psbt.md

WHAT IT DOES

What sign_btc_multisig_psbt does on VaultPilot MCP

AI agents call sign_btc_multisig_psbt 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
`psbtBase64`	string	Yes	Base64-encoded PSBT v0 from the initiator. Every input must carry a `bip32_derivation` entry for our master fingerprint, or we refuse to forward to the device.
`walletName`	string	Yes	Name of a previously-registered multi-sig wallet (matches the `name` passed to `register_btc_multisig_wallet`). Refused if no wallet is registered under this na

Parameters from the server's own tool schema.

RISK

Why sign_btc_multisig_psbt is rated Low

Even though sign_btc_multisig_psbt 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

RECOMMENDED RULE

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

sign_btc_multisig_psbt Allowed

sign_btc_multisig_psbt is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sign_btc_multisig_psbt": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sign_btc_multisig_psbt

What does the sign_btc_multisig_psbt tool do? +

Co-signer flow — adds OUR Ledger signature to a multi-sig PSBT produced by an external initiator (Sparrow / Specter / Caravan / a peer running this server). Looks up the registered wallet by name, decodes the PSBT, validates every input carries a bip32_derivation entry for our master fingerprint (defense against being tricked into signing for a foreign tx), forwards to the Ledger device for the on-device output walkthrough (the user MUST verify every output address + amount on-device matches the chat-side verification block before approving), splices our partial signature(s) into the PSBT, returns the partial PSBT for the user to share back to the coordinator. We do NOT finalize or broadcast — that's the initiator's job once they have all M signatures. Phase 2 scope: P2WSH wallets registered via register_btc_multisig_wallet. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does sign_btc_multisig_psbt accept? +

sign_btc_multisig_psbt accepts 2 parameters: psbtBase64, walletName. Required: psbtBase64, walletName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sign_btc_multisig_psbt? +

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

sign_btc_multisig_psbt is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sign_btc_multisig_psbt? +

Yes. Add a rate_limit block to the sign_btc_multisig_psbt 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 sign_btc_multisig_psbt completely? +

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

sign_btc_multisig_psbt 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →