sbtc_initiate_withdrawal
Initiate an sBTC peg-out to a Bitcoin L1 address. Locks (amount + maxFee) of sBTC in the sBTC protocol and creates a withdrawal request. Signers later process the request and send BTC on L1.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/sbtc-initiate-withdrawal.md
What sbtc_initiate_withdrawal does on Aibtc
AI agents use sbtc_initiate_withdrawal to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why sbtc_initiate_withdrawal is rated Critical
This tool moves real financial assets (sBTC/BTC) by initiating a peg-out (withdrawal) from the sBTC protocol to a Bitcoin L1 address. It locks funds and triggers an irreversible cross-chain transfer of cryptocurrency, squarely placing it in the Financial category with critical severity due to the potential for significant monetary loss if misused.
From the tool's definition Initiate an sBTC peg-out to a Bitcoin L1 address. Locks (amount + maxFee) of sBTC in the sBTC protocol and creates a withdrawal request. Signers later process the request and send BTC on L1.
Attacks that exploit this kind of access
The rule that runs sbtc_initiate_withdrawal 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 sbtc_initiate_withdrawal, this is the rule to start with:
Any call to sbtc_initiate_withdrawal is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every sbtc_initiate_withdrawal call is checked against it from then on.
Questions about sbtc_initiate_withdrawal
Initiate an sBTC peg-out to a Bitcoin L1 address. Locks (amount + maxFee) of sBTC in the sBTC protocol and creates a withdrawal request. Signers later process the request and send BTC on L1. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for sbtc_initiate_withdrawal: 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.
sbtc_initiate_withdrawal is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the sbtc_initiate_withdrawal 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.
Set action: deny in the PolicyLayer policy for sbtc_initiate_withdrawal. 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.
sbtc_initiate_withdrawal 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.
More on Aibtc, and thousands of servers like it.
Across the catalogue