pillar_dca_status

Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-dca-status.md

WHAT IT DOES

What pillar_dca_status does on Aibtc

AI agents call pillar_dca_status to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pillar_dca_status is rated Low

This tool retrieves information about Dollar-Cost Averaging (DCA) schedules and their progress. It performs a read-only query operation that returns existing data without creating, modifying, executing commands, deleting data, or moving funds. No side effects are indicated.

From the tool's definition Tool name and description indicate a query/status check operation: 'Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress.' The verb 'check' and 'shows' indicate data retrieval with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pillar_dca_status 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_dca_status, this is the rule to start with:

pillar_dca_status Allowed

pillar_dca_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pillar_dca_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every pillar_dca_status call is checked against it from then on.

FAQ

Questions about pillar_dca_status

What does the pillar_dca_status tool do? +

Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pillar_dca_status? +

Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_dca_status: 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.

What risk level is pillar_dca_status? +

pillar_dca_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pillar_dca_status? +

Yes. Add a rate_limit block to the pillar_dca_status 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.

How do I block pillar_dca_status completely? +

Set action: deny in the PolicyLayer policy for pillar_dca_status. 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_dca_status? +

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

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →