wallet_abortAction
Aborts a pending (nosend or unsigned) transaction, releasing consumed inputs back to spendable state.
This record as markdown: /tools/b-open-io-bsv-mcp/wallet-abortaction.md
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.
Why wallet_abortAction is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs wallet_abortAction 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_abortAction, this is the rule to start with:
wallet_abortAction is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin SV MCP Server, apply this rule, and every wallet_abortAction call is checked against it from then on.
Questions about wallet_abortAction
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.
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.
wallet_abortAction is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
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.
More on Bitcoin SV MCP Server, and thousands of servers like it.
Across the catalogue