Critical Risk →

wallet_abortAction

Aborts a pending (nosend or unsigned) transaction, releasing consumed inputs back to spendable state.

How to control wallet_abortAction ↓

What wallet_abortAction does on Bitcoin SV MCP Server

AI agents call wallet_abortAction 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_abortAction needs a policy

Aborting a transaction is an irreversible cancellation of that pending action. Once aborted, the transaction cannot be recovered or re-submitted; the operation permanently discards the prepared transaction. While it releases inputs back to spendable state (which could be seen as reversible from a funds perspective), the transaction itself is irreversibly destroyed, fitting the Destructive category.

From the tool's definition Aborts a pending (nosend or unsigned) transaction, releasing consumed inputs back to spendable state.

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

How to control wallet_abortAction

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

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

wallet_abortAction 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_abortAction

What does the wallet_abortAction tool do? +

Aborts a pending (nosend or unsigned) transaction, releasing consumed inputs back to spendable state. 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_abortAction? +

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

wallet_abortAction 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_abortAction? +

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

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

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