Critical Risk →

wallet_relinquishOutput

Removes an output from a basket without spending it.

How to control wallet_relinquishOutput ↓

What wallet_relinquishOutput does on Bitcoin SV MCP Server

AI agents call wallet_relinquishOutput 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_relinquishOutput needs a policy

Removing an output from a basket is a destructive, irreversible action — the association between the UTXO and the basket is permanently severed. This cannot be undone without re-adding the output, and misuse could cause loss of access to funds or NFTs tracked in that basket, making it high severity.

From the tool's definition Removes an output from a basket without spending it

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

How to control wallet_relinquishOutput

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_relinquishOutput:

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

wallet_relinquishOutput 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_relinquishOutput

What does the wallet_relinquishOutput tool do? +

Removes an output from a basket without spending it. 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_relinquishOutput? +

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

wallet_relinquishOutput 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_relinquishOutput? +

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

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

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