pillar_direct_dca_partners
View your DCA partners and weekly status.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-direct-dca-partners.md
What pillar_direct_dca_partners does on Aibtc
AI agents call pillar_direct_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.
Why pillar_direct_dca_partners is rated Low
This tool queries and displays user data (DCA partners and their status) with no side effects, no code execution, no data modification, and no financial transactions initiated. It is a read-only retrieval operation. Confidence is not higher because the server description is absent and 'DCA' context suggests a financial service, but the tool itself performs only viewing/listing operations, not financial movements.
From the tool's definition Tool name includes 'View' action and description states 'View your DCA partners and weekly status' - purely retrieves information about existing DCA (Dollar-Cost Averaging) partnerships without modification or execution.
Attacks that exploit this kind of access
The rule that runs pillar_direct_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_direct_dca_partners, this is the rule to start with:
pillar_direct_dca_partners is read-only, so it stays allowed. 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_direct_dca_partners call is checked against it from then on.
Questions about pillar_direct_dca_partners
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.
Register the Aibtc MCP server in PolicyLayer and add a rule for pillar_direct_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.
pillar_direct_dca_partners is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pillar_direct_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.
Set action: deny in the PolicyLayer policy for pillar_direct_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.
pillar_direct_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.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue