wallet_remove

Remove a local account only with force, backup confirmation and human approval. Fund absence cannot be proven across all derived addresses. Cannot remove the active account; never sweeps funds.

SERVERBitcoin SV MCP Server SOURCEb-open-io/bsv-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/b-open-io-bsv-mcp/wallet-remove.md

WHAT IT DOES

What wallet_remove does on Bitcoin SV MCP Server

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

RISK

Why wallet_remove is rated Critical

Permanently removes a wallet account; irreversible deletion even without fund sweeping.

From the tool's definition Remove a local account only with force, backup confirmation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wallet_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin SV MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_remove, this is the rule to start with:

wallet_remove Hidden

wallet_remove 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": [
    "wallet_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about wallet_remove

What does the wallet_remove tool do? +

Remove a local account only with force, backup confirmation and human approval. Fund absence cannot be proven across all derived addresses. Cannot remove the active account; never sweeps funds. It is categorised as a Destructive tool in the Bitcoin SV MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on wallet_remove? +

Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_remove: 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 Bitcoin SV MCP Server. Nothing to install.

What risk level is wallet_remove? +

wallet_remove 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 wallet_remove? +

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

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

wallet_remove is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bitcoin SV MCP Server, and thousands of servers like it.

This server

All 90 Bitcoin SV MCP Server tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →