pillar_direct_auto_compound

Configure auto-compound for your Pillar wallet. When enabled, a keeper automatically boosts when sBTC accumulates above the trigger. Agent-signed, no browser needed. Backend sponsors gas.

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

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke pillar_direct_auto_compound 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.

// WHY ENFORCE A POLICY ON PILLAR_DIRECT_AUTO_COMPOUND

pillar_direct_auto_compound 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.

// RECOMMENDED POLICY

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

io-github-aibtcdev-mcp-server.yaml

tools:
  pillar_direct_auto_compound:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Aibtc policy for all 288 tools.

// DETAILS

Tool Name pillar_direct_auto_compound

Category Execute

MCP Server Aibtc MCP Server

Risk Level High

// MORE AIBTC TOOLS

Financial identity_transfer Financial jingswap_deposit_sbtc Financial jingswap_deposit_stx Financial ordinals_p2p_transfer Financial pillar_direct_withdraw_collateral Financial sbtc_deposit Financial sbtc_transfer Financial sbtc_withdraw

View all 288 tools →

// RELATED READING

// FAQ

What does the pillar_direct_auto_compound tool do? +

Configure auto-compound for your Pillar wallet. When enabled, a keeper automatically boosts when sBTC accumulates above the trigger. Agent-signed, no browser needed. Backend sponsors gas.. 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 pillar_direct_auto_compound? +

Add a rule in your Intercept YAML policy under the tools section for pillar_direct_auto_compound. 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 pillar_direct_auto_compound? +

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

Can I rate-limit pillar_direct_auto_compound? +

Yes. Add a rate_limit block to the pillar_direct_auto_compound 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 pillar_direct_auto_compound completely? +

Set action: deny in the Intercept policy for pillar_direct_auto_compound. 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 pillar_direct_auto_compound? +

pillar_direct_auto_compound 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.

pillar_direct_auto_compound

Enforce policies on Aibtc