sbtc_deposit
Deposit BTC to receive sBTC on Stacks L2. This builds, signs, and broadcasts a Bitcoin transaction to the sBTC deposit address. After confirmation, sBTC tokens are minted to your Stacks address. The transaction uses your wallet
This record as markdown: /tools/io-github-aibtcdev-mcp-server/sbtc-deposit.md
What sbtc_deposit does on Aibtc
AI agents use sbtc_deposit to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why sbtc_deposit is rated Critical
This tool directly moves money (BTC) and commits financial obligations by broadcasting a blockchain transaction. The user's cryptocurrency is transferred and converted to sBTC tokens. This is an irreversible financial transaction with maximum severity—misuse by an agent could drain the user's Bitcoin holdings.
From the tool's definition Tool description states: 'Deposit BTC to receive sBTC on Stacks L2' and 'builds, signs, and broadcasts a Bitcoin transaction' and 'uses your wallet'.
Attacks that exploit this kind of access
The rule that runs sbtc_deposit 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_deposit, this is the rule to start with:
Any call to sbtc_deposit 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_deposit call is checked against it from then on.
Questions about sbtc_deposit
Deposit BTC to receive sBTC on Stacks L2. This builds, signs, and broadcasts a Bitcoin transaction to the sBTC deposit address. After confirmation, sBTC tokens are minted to your Stacks address. The transaction uses your wallet. 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_deposit: 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_deposit 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_deposit 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_deposit. 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_deposit 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