Creates a DCA bot that automatically invests at regular intervals.\nSpecify investment frequency (in seconds), quote coin, trading pairs\nwith individual amounts, and optional max investment amount.\n\nPrerequisites:\n- User must be authenticated and pass KYC/compliance checks.\n- Trading pairs m...
AI agents use createDCABot to commit financial operations through Bybit MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates an automated trading bot that repeatedly commits financial transactions (purchases of cryptocurrency) at regular intervals. It directly triggers ongoing financial obligations on a live cryptocurrency exchange, making it Financial category with critical severity due to the automated and recurring nature of the investments.
From the tool's definition Creates a DCA bot that automatically invests at regular intervals... investment frequency... quote coin, trading pairs with individual amounts... optional max investment amount
Documented attack patterns abuse exactly the kind of access createDCABot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for createDCABot:
{
"version": "1",
"default": "deny",
"tools": {
"createDCABot": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to createDCABot is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Creates a DCA bot that automatically invests at regular intervals.\nSpecify investment frequency (in seconds), quote coin, trading pairs\nwith individual amounts, and optional max investment amount.\n\nPrerequisites:\n- User must be authenticated and pass KYC/compliance checks.\n- Trading pairs must be valid and not duplicated.\n- Minimum frequency is 10 seconds.\n- Maximum 5 trading pairs per bot.\n\nReturns bot_id on success. If the user is banned (status_code=421),\nban_reason_text provides a localized explanation.\n\nRate limit: 3 qps per UID.\n\nAgent hint: The parameters.frequency_in_second field controls how often the bot\ninvests. Common values: 600 (10 min), 3600 (1 hour), 86400 (1 day).\nEach pair in parameters.pairs specifies a base coin and its per-round\ninvestment amount. It is categorised as a Financial tool in the Bybit MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for createDCABot: 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 Bybit MCP Server. Nothing to install.
createDCABot is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the createDCABot 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 createDCABot. 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.
createDCABot is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bybit MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.