nostr_sign_event

Accepts raw HTML/template content (content)

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 nostr_sign_event 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 NOSTR_SIGN_EVENT

Even though nostr_sign_event 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:
  nostr_sign_event:
    rules:
      - action: allow

See the full Aibtc policy for all 288 tools.

// DETAILS

Tool Name nostr_sign_event

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 nostr_sign_event tool do? +

Sign a Nostr event (NIP-01) using BIP-340 Schnorr. Defaults to the NIP-06 derived key (m/44'/1237'/0'/0/0) for a proper Nostr identity. Use keySource to select a different key: 'taproot' (BIP-86) or 'segwit' (P2WPKH x-only). Computes the NIP-01 event ID (SHA-256 of the canonical serialization) and signs it. Returns the complete signed event ready to publish to Nostr relays. Requires an unlocked wallet.. 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 nostr_sign_event? +

Add a rule in your Intercept YAML policy under the tools section for nostr_sign_event. 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 nostr_sign_event? +

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

Can I rate-limit nostr_sign_event? +

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

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

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

nostr_sign_event

Enforce policies on Aibtc