Critical Risk →

wallet_relinquishCertificate

Removes a certificate from the wallet.

How to control wallet_relinquishCertificate ↓

What wallet_relinquishCertificate does on Bitcoin SV MCP Server

AI agents call wallet_relinquishCertificate 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.

Critical Risk

Why wallet_relinquishCertificate needs a policy

The tool irreversibly removes a certificate from the wallet. Deletion/removal of cryptographic certificates from a blockchain wallet is a destructive, likely irreversible action. Misuse by an AI agent could result in permanent loss of identity credentials or access rights on the BSV blockchain.

From the tool's definition Removes a certificate from the wallet

Documented attack patterns abuse exactly the kind of access wallet_relinquishCertificate gives an agent:

How to control wallet_relinquishCertificate

PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin SV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wallet_relinquishCertificate:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "wallet_relinquishCertificate"
  ]
}

wallet_relinquishCertificate disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Bitcoin SV MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about wallet_relinquishCertificate

What does the wallet_relinquishCertificate tool do? +

Removes a certificate from the wallet. 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_relinquishCertificate? +

Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for wallet_relinquishCertificate: 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_relinquishCertificate? +

wallet_relinquishCertificate 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_relinquishCertificate? +

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

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

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

Enforce policy on every Bitcoin SV MCP Server tool call.

Start from Bitcoin SV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

80 Bitcoin SV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.