Medium Risk

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.

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

AI agents use sbtc_initiate_withdrawal to create or modify resources in Aibtc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call sbtc_initiate_withdrawal repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Aibtc.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-aibtcdev-mcp-server.yaml
tools:
  sbtc_initiate_withdrawal:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Aibtc policy for all 308 tools.

Tool Name sbtc_initiate_withdrawal
Category Write
MCP Server Aibtc MCP Server
Risk Level Medium

View all 308 tools →

Agents calling write-class tools like sbtc_initiate_withdrawal have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the sbtc_initiate_withdrawal tool do? +

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 Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sbtc_initiate_withdrawal? +

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

sbtc_initiate_withdrawal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sbtc_initiate_withdrawal? +

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

Set action: deny in the Intercept 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.

What MCP server provides sbtc_initiate_withdrawal? +

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

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.