sbtc_withdraw

Alias for sbtc_initiate_withdrawal. Initiates an sBTC peg-out request to BTC L1.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/sbtc-withdraw.md

WHAT IT DOES

What sbtc_withdraw does on Aibtc

AI agents use sbtc_withdraw to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why sbtc_withdraw is rated Critical

This tool directly moves or commits financial value by initiating a withdrawal of sBTC (a Bitcoin-backed token) to the Bitcoin Layer 1 blockchain. A peg-out transaction irreversibly transfers cryptocurrency assets from one chain to another, making it a financial operation.

From the tool's definition Tool description states it 'Initiates an sBTC peg-out request to BTC L1' - a peg-out involves converting wrapped sBTC tokens back to native Bitcoin on Layer 1, which constitutes a movement of cryptocurrency assets.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sbtc_withdraw 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_withdraw, this is the rule to start with:

sbtc_withdraw Approval-gated

Any call to sbtc_withdraw is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sbtc_withdraw": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sbtc_withdraw

What does the sbtc_withdraw tool do? +

Alias for sbtc_initiate_withdrawal. Initiates an sBTC peg-out request to BTC 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.

How do I enforce a policy on sbtc_withdraw? +

Register the Aibtc MCP server in PolicyLayer and add a rule for sbtc_withdraw: 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 sbtc_withdraw? +

sbtc_withdraw is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sbtc_withdraw? +

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

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

sbtc_withdraw 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 → Critical-risk tools on this server →

Across the catalogue

build_redeem_withdraw_tx on Atv →withdraw_coin on Indodax MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →