High Risk →

wallet_signAction

Signs a transaction previously created with createAction (when signAndProcess was false).

How to control wallet_signAction ↓

What wallet_signAction does on Bitcoin SV MCP Server

AI agents invoke wallet_signAction to trigger actions in Bitcoin SV MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why wallet_signAction needs a policy

Signing a blockchain transaction is a critical step in executing it on-chain. While signing itself doesn't broadcast the transaction, it is a necessary execution step that authorizes and enables a BSV blockchain transaction to be processed.

From the tool's definition Signs a transaction previously created with createAction (when signAndProcess was false)

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

How to control wallet_signAction

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wallet_signAction": {
      "limits": [
        {
          "counter": "wallet_signaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

wallet_signAction stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about wallet_signAction

What does the wallet_signAction tool do? +

Signs a transaction previously created with createAction (when signAndProcess was false). It is categorised as a Execute tool in the Bitcoin SV MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wallet_signAction? +

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

wallet_signAction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wallet_signAction? +

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

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

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