High Risk

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.

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@aibtc/mcp-server Execute Risk 3/5

AI agents invoke dual_stacking_opt_out to trigger processes or run actions in Aibtc. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

dual_stacking_opt_out can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-aibtcdev-mcp-server.yaml
tools:
  dual_stacking_opt_out:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Aibtc policy for all 288 tools.

Tool Name dual_stacking_opt_out
Category Execute
MCP Server Aibtc MCP Server
Risk Level High

View all 288 tools →

What does the dual_stacking_opt_out tool do? +

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.

How do I enforce a policy on dual_stacking_opt_out? +

Add a rule in your Intercept YAML policy under the tools section for dual_stacking_opt_out. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

What risk level is dual_stacking_opt_out? +

dual_stacking_opt_out is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit dual_stacking_opt_out? +

Yes. Add a rate_limit block to the dual_stacking_opt_out rule in your Intercept 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.

How do I block dual_stacking_opt_out completely? +

Set action: deny in the Intercept 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.

What MCP server provides dual_stacking_opt_out? +

dual_stacking_opt_out is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Aibtc

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.