pillar_dca_partners

View your DCA partners and weekly status.

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-partners.md

WHAT IT DOES

What pillar_dca_partners does on Aibtc

AI agents call pillar_dca_partners 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_partners is rated Low

This tool retrieves or queries information about DCA (Dollar-Cost Averaging) partners and their status. No modification, execution, deletion, or financial transaction occurs—it only displays existing data to the user. This is consistent with the 'Read' category for tools that retrieve or query data without side effects.

From the tool's definition Tool name and description indicate viewing/querying data: 'View your DCA partners and weekly status.' The verb 'view' and the passive retrieval of status information suggest a read-only operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pillar_dca_partners Allowed

pillar_dca_partners 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_partners": {}
  }
}

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_partners call is checked against it from then on.

FAQ

Questions about pillar_dca_partners

What does the pillar_dca_partners tool do? +

View your DCA partners and weekly status. 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_partners? +

Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_dca_partners: 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_partners? +

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

Can I rate-limit pillar_dca_partners? +

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

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

pillar_dca_partners 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

The MCP Attack Database →

Guides

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