styx_deposit
Full headless BTC→sBTC deposit via the Styx protocol.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/styx-deposit.md
What styx_deposit does on Aibtc
AI agents use styx_deposit to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why styx_deposit is rated Critical
This tool moves cryptocurrency (Bitcoin to synthetic Bitcoin), which constitutes a financial transaction with real monetary consequences. The 'headless' design suggests it can execute without interactive confirmation, increasing misuse risk. An AI agent invoking this without explicit user intent could irreversibly transfer funds.
From the tool's definition Tool name 'styx_deposit' and description 'Full headless BTC→sBTC deposit via the Styx protocol' indicate a cryptocurrency deposit operation that commits financial value (BTC to sBTC conversion).
Attacks that exploit this kind of access
The rule that runs styx_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 styx_deposit, this is the rule to start with:
Any call to styx_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 styx_deposit call is checked against it from then on.
Questions about styx_deposit
Full headless BTC→sBTC deposit via the Styx protocol. 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 styx_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.
styx_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 styx_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 styx_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.
styx_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