wallet_delete

Permanently delete a wallet. WARNING: This cannot be undone! Make sure you have backed up your mnemonic.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/wallet-delete.md

WHAT IT DOES

What wallet_delete does on Aibtc

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

RISK

Why wallet_delete is rated Critical

This tool permanently deletes a wallet, which is an irreversible destructive action. The description's warning that 'This cannot be undone' confirms it meets the Destructive category criteria. Given that wallets contain cryptographic keys and financial assets, misuse would result in total loss of funds and access, warranting critical severity.

From the tool's definition Tool name 'wallet_delete' and description 'Permanently delete a wallet. WARNING: This cannot be undone! Make sure you have backed up your mnemonic.' explicitly indicate irreversible deletion of financial data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wallet_delete safely

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

wallet_delete Hidden

wallet_delete 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_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about wallet_delete

What does the wallet_delete tool do? +

Permanently delete a wallet. WARNING: This cannot be undone! Make sure you have backed up your mnemonic. It is categorised as a Destructive tool in the Aibtc 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_delete? +

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

What risk level is wallet_delete? +

wallet_delete 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_delete? +

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

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

wallet_delete is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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