Execute complete BTC to sBTC swap using Keeper system
AI agents use bitflow_execute_btc_to_sbtc_keeper_order to commit financial operations through Stacks AI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool executes a cryptocurrency swap between BTC and sBTC, directly moving financial assets. It commits real funds on-chain and cannot be reversed once executed. The use of 'Execute' combined with a cross-chain swap involving Bitcoin makes this a high-blast-radius financial operation — misuse by an AI agent could result in irreversible loss of funds.
From the tool's definition Execute complete BTC to sBTC swap using Keeper system
Attacks that exploit this kind of access
Execute complete BTC to sBTC swap using Keeper system. It is categorised as a Financial tool in the Stacks AI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for bitflow_execute_btc_to_sbtc_keeper_order: 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 Stacks AI MCP Server. Nothing to install.
bitflow_execute_btc_to_sbtc_keeper_order 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 bitflow_execute_btc_to_sbtc_keeper_order 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 bitflow_execute_btc_to_sbtc_keeper_order. 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.
bitflow_execute_btc_to_sbtc_keeper_order is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →