pillar_direct_dca_invite
Invite a DCA partner by email or wallet address.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-direct-dca-invite.md
What pillar_direct_dca_invite does on Aibtc
AI agents use pillar_direct_dca_invite 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_direct_dca_invite is rated Medium
This tool creates new invitation records and establishes connections between users, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move funds. While invitations could potentially be abused to spam users, the primary function is data creation/modification rather than destruction or financial transfer.
From the tool's definition The tool name 'pillar_direct_dca_invite' and description 'Invite a DCA partner by email or wallet address' indicate it creates or modifies state by adding a new invitation record.
Attacks that exploit this kind of access
The rule that runs pillar_direct_dca_invite 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_invite, this is the rule to start with:
pillar_direct_dca_invite 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_direct_dca_invite call is checked against it from then on.
Questions about pillar_direct_dca_invite
Invite a DCA partner by email or wallet address. 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_direct_dca_invite: 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_invite 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_direct_dca_invite 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_invite. 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_invite 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