extend_stacking
Update an existing PoX-5 stake: extend the lock, add STX, switch signer manager, or change payout calldata (pox-5 stake-update). Any combination in one call. Increasing locks more of the address
This record as markdown: /tools/io-github-aibtcdev-mcp-server/extend-stacking.md
What extend_stacking does on Aibtc
AI agents use extend_stacking to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why extend_stacking is rated Critical
Modifies financial staking commitments by locking STX and changing payout configurations.
From the tool's definition extend the lock, add STX, switch signer manager, change payout calldata
Attacks that exploit this kind of access
The rule that runs extend_stacking 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 extend_stacking, this is the rule to start with:
Any call to extend_stacking 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 extend_stacking call is checked against it from then on.
Questions about extend_stacking
Update an existing PoX-5 stake: extend the lock, add STX, switch signer manager, or change payout calldata (pox-5 stake-update). Any combination in one call. Increasing locks more of the address. 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 extend_stacking: 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.
extend_stacking 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 extend_stacking 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 extend_stacking. 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.
extend_stacking 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