pillar_auto_compound
Configure auto-compound for your Pillar wallet.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-auto-compound.md
What pillar_auto_compound does on Aibtc
AI agents use pillar_auto_compound to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why pillar_auto_compound is rated Medium
The tool modifies wallet configuration (enabling/disabling auto-compounding), which is a reversible write operation. It does not execute arbitrary code, delete data, or move funds directly, but misconfiguration could lead to unintended financial outcomes. Severity is high because wallet configuration changes affect financial assets and could result in losses if misconfigured by an unreliable agent.
From the tool's definition Tool name 'pillar_auto_compound' combined with description 'Configure auto-compound for your Pillar wallet' indicates modification of wallet configuration settings.
Attacks that exploit this kind of access
The rule that runs pillar_auto_compound 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 pillar_auto_compound, this is the rule to start with:
pillar_auto_compound stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 pillar_auto_compound call is checked against it from then on.
Questions about pillar_auto_compound
Configure auto-compound for your Pillar wallet. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_auto_compound: 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.
pillar_auto_compound is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pillar_auto_compound 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 pillar_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.
pillar_auto_compound 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.
This server
Across the catalogue