btc_sign_message

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents call btc_sign_message to retrieve information from Aibtc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON BTC_SIGN_MESSAGE

Even though btc_sign_message only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-aibtcdev-mcp-server.yaml

tools:
  btc_sign_message:
    rules:
      - action: allow

See the full Aibtc policy for all 288 tools.

// DETAILS

Tool Name btc_sign_message

Category Read

MCP Server Aibtc MCP Server

Risk Level Low

// MORE AIBTC TOOLS

Financial identity_transfer Financial jingswap_deposit_sbtc Financial jingswap_deposit_stx Financial ordinals_p2p_transfer Financial pillar_direct_withdraw_collateral Financial sbtc_deposit Financial sbtc_transfer Financial sbtc_withdraw

View all 288 tools →

// RELATED READING

// FAQ

What does the btc_sign_message tool do? +

Sign a plain text message using Bitcoin message signing. Automatically selects BIP-322 for native SegWit (bc1q) and Taproot (bc1p) addresses, and BIP-137 for legacy (1...) and wrapped SegWit (3...) addresses. Use addressType 'p2tr' to force signing with the Taproot key. Use cases: proving Bitcoin address ownership, authentication, off-chain verification. Requires an unlocked wallet with Bitcoin keys.. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on btc_sign_message? +

Add a rule in your Intercept YAML policy under the tools section for btc_sign_message. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

What risk level is btc_sign_message? +

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

Can I rate-limit btc_sign_message? +

Yes. Add a rate_limit block to the btc_sign_message rule in your Intercept 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 btc_sign_message completely? +

Set action: deny in the Intercept policy for btc_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 btc_sign_message? +

btc_sign_message is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

btc_sign_message

Enforce policies on Aibtc