psbt_sign

Sign one or more PSBT inputs with the active wallet. Supports buyer (P2WPKH) and taproot keys.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/psbt-sign.md

WHAT IT DOES

What psbt_sign does on Aibtc

AI agents invoke psbt_sign to trigger actions in Aibtc. 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.

RISK

Why psbt_sign is rated High

Signing a PSBT (Partially Signed Bitcoin Transaction) is an execution action that uses cryptographic wallet keys to authorize a Bitcoin transaction. While it doesn't directly move funds (that would be broadcasting/submitting), signing is a critical step that enables financial transactions. It triggers an external cryptographic operation with the active wallet.

From the tool's definition Sign one or more PSBT inputs with the active wallet. Supports buyer (P2WPKH) and taproot keys.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs psbt_sign safely

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

psbt_sign Rate-limited

psbt_sign 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": {
    "psbt_sign": {
      "limits": [
        {
          "counter": "psbt_sign_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every psbt_sign call is checked against it from then on.

FAQ

Questions about psbt_sign

What does the psbt_sign tool do? +

Sign one or more PSBT inputs with the active wallet. Supports buyer (P2WPKH) and taproot keys. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on psbt_sign? +

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

What risk level is psbt_sign? +

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

Can I rate-limit psbt_sign? +

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

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

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

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →