stx_sign_transactions · Bitcoin wallet MCP server MCP

WHAT IT DOES

What stx_sign_transactions does on Bitcoin wallet MCP server

AI agents invoke stx_sign_transactions to trigger actions in Bitcoin wallet 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.

WHY IT NEEDS A POLICY

Why stx_sign_transactions needs a policy

Signing transactions is a critical cryptographic operation that authorizes blockchain transactions for broadcast. While signing alone doesn't move funds immediately, it produces signed artifacts that, once broadcast, execute financial transfers. It spans Execute and Financial categories; since signing is a prerequisite step to financial operations but doesn't itself move money, Execute is the most precise category.

From the tool's definition Sign multiple Stacks transactions in batch

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stx_sign_transactions Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stx_sign_transactions": {
      "limits": [
        {
          "counter": "stx_sign_transactions_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bitcoin wallet MCP server, so you can run agents against it safely.

FAQ

Questions about stx_sign_transactions

What does the stx_sign_transactions tool do? +

Sign multiple Stacks transactions in batch. It is categorised as a Execute tool in the Bitcoin wallet 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 stx_sign_transactions? +

Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for stx_sign_transactions: 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 wallet MCP server. Nothing to install.

What risk level is stx_sign_transactions? +

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

Can I rate-limit stx_sign_transactions? +

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

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

stx_sign_transactions is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.