stx_sign_message

Sign a UTF-8 message on Stacks. Returns recoverable ECDSA signature

SERVERBitcoin wallet MCP server SOURCEmarkmhendrickson/mcp-server-bitcoin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/stx-sign-message.md

WHAT IT DOES

What stx_sign_message does on Bitcoin wallet MCP server

AI agents call stx_sign_message to retrieve information from Bitcoin wallet MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why stx_sign_message is rated Low

Message signing with a private key produces a cryptographic signature but does not broadcast transactions, move funds, or modify state. It is a local cryptographic operation. However, signing can be a precursor to financial operations, and misuse (e.g., signing authorization messages) could have downstream consequences.

From the tool's definition Sign a UTF-8 message on Stacks. Returns recoverable ECDSA signature

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stx_sign_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin wallet MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stx_sign_message, this is the rule to start with:

stx_sign_message Allowed

stx_sign_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stx_sign_message": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin wallet MCP server, apply this rule, and every stx_sign_message call is checked against it from then on.

FAQ

Questions about stx_sign_message

What does the stx_sign_message tool do? +

Sign a UTF-8 message on Stacks. Returns recoverable ECDSA signature. It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on stx_sign_message? +

Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for stx_sign_message: 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_message? +

stx_sign_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit stx_sign_message? +

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

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

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

KEEP EXPLORING

More on Bitcoin wallet MCP server, and thousands of servers like it.

This server

All 93 Bitcoin wallet MCP server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →