unregister_btc_multisig_wallet

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Critical RISK CLASS

Category Destructive

Parameters 11 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What unregister_btc_multisig_wallet does on VaultPilot MCP

AI agents call unregister_btc_multisig_wallet to permanently remove resources in VaultPilot MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`walletName`	string	Yes	Name of the wallet to drop from the local cache. Idempotent — succeeds with `removed: false` when the name isn't registered. The Ledger device retains the polic

Parameters from the server's own tool schema.

RISK

Why unregister_btc_multisig_wallet is rated Critical

This tool irreversibly deletes wallet registration metadata from local storage. Although it does not directly move funds or execute transactions, destroying wallet configuration data in a crypto custody context is a destructive action because: (1) it removes the association between a wallet name and its descriptor/cosigner configuration, (2) re-registration requires knowing the exact descriptor and cosigners, and…

From the tool's definition Tool description explicitly uses the word "Drop" and describes removing wallet registration from local cache. The function "unregister" combined with "Drop" indicates irreversible removal of configuration data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

unregister_btc_multisig_wallet Hidden

unregister_btc_multisig_wallet is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "unregister_btc_multisig_wallet"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about unregister_btc_multisig_wallet

What does the unregister_btc_multisig_wallet tool do? +

Drop a registered multi-sig wallet from the local cache. The Ledger device retains the policy HMAC indefinitely (no on-device unregister API), so re-registering with the SAME descriptor + cosigners returns the same HMAC the device already has. This tool only forgets the local-disk entry — call it before re-registering with different cosigners under the same name, or to clean up wallets you no longer use. Idempotent: returns removed: false when the name isn't registered. No device touch. It is categorised as a Destructive tool in the VaultPilot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does unregister_btc_multisig_wallet accept? +

unregister_btc_multisig_wallet accepts 1 parameter: walletName. Required: walletName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on unregister_btc_multisig_wallet? +

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

unregister_btc_multisig_wallet is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit unregister_btc_multisig_wallet? +

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

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

unregister_btc_multisig_wallet 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 → Critical-risk tools on this server →

Across the catalogue

unregister_passenger_app on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →