stack_stx
Lock STX for stacking to earn BTC rewards. Requires a Bitcoin address (hash) for receiving rewards.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/stack-stx.md
What stack_stx does on Aibtc
AI agents use stack_stx to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why stack_stx is rated Critical
This tool locks STX tokens (a financial asset) and commits them to a stacking contract to earn BTC rewards. This involves moving/locking cryptocurrency assets, which constitutes a financial commitment. Misuse could result in funds being locked or lost, making it critical severity.
From the tool's definition Lock STX for stacking to earn BTC rewards
Attacks that exploit this kind of access
The rule that runs stack_stx 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 stack_stx, this is the rule to start with:
Any call to stack_stx 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 stack_stx call is checked against it from then on.
Questions about stack_stx
Lock STX for stacking to earn BTC rewards. Requires a Bitcoin address (hash) for receiving rewards. 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 stack_stx: 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.
stack_stx 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 stack_stx 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 stack_stx. 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.
stack_stx 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