wallet_relinquishCertificate

Removes a certificate from the wallet.

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-relinquishcertificate.md

WHAT IT DOES

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.

RISK

Why wallet_relinquishCertificate is rated Critical

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wallet_relinquishCertificate Hidden

wallet_relinquishCertificate 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_relinquishCertificate"
  ]
}

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_relinquishCertificate call is checked against it from then on.

FAQ

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.

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

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →