dual_stacking_opt_out
Opt out of Dual Stacking. Removes your wallet from the Dual Stacking protocol. The opt-out takes effect at the start of the next PoX cycle; you continue to earn rewards for the current cycle. Requires an unlocked wallet. Note: Dual Stacking is only available on mainnet.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/dual-stacking-opt-out.md
What dual_stacking_opt_out does on Aibtc
AI agents invoke dual_stacking_opt_out to trigger actions in Aibtc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why dual_stacking_opt_out is rated High
This tool triggers an on-chain transaction that removes the wallet from the Dual Stacking protocol. While it doesn't delete data or move money directly, it executes an external blockchain operation with real financial consequences (loss of future stacking rewards).
From the tool's definition Opt out of Dual Stacking. Removes your wallet from the Dual Stacking protocol.
Attacks that exploit this kind of access
The rule that runs dual_stacking_opt_out 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 dual_stacking_opt_out, this is the rule to start with:
dual_stacking_opt_out stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every dual_stacking_opt_out call is checked against it from then on.
Questions about dual_stacking_opt_out
Opt out of Dual Stacking. Removes your wallet from the Dual Stacking protocol. The opt-out takes effect at the start of the next PoX cycle; you continue to earn rewards for the current cycle. Requires an unlocked wallet. Note: Dual Stacking is only available on mainnet. It is categorised as a Execute tool in the Aibtc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Aibtc MCP server in PolicyLayer and add a rule for dual_stacking_opt_out: 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.
dual_stacking_opt_out is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dual_stacking_opt_out 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 dual_stacking_opt_out. 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.
dual_stacking_opt_out 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