Closes a running DCA bot. You must specify a close_mode to determine\nhow remaining assets are settled:\n- 1 (DCA_BIT_MODE): settle in BIT\n- 2 (DCA_BASE_MODE): convert all to base tokens\n- 3 (DCA_QUOTE_MODE): convert all to quote token\n\nThe bot must be in a closeable state. Bots that are curr...
AI agents use closeDCABot to create or update resources in Bybit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.
This tool modifies the state of a DCA (Dollar-Cost Averaging) bot and converts/settles cryptocurrency assets, which constitutes a Write action with financial implications. While it involves asset conversion (which could approach Destructive or Financial severity), it is reversible in nature—users can restart bots or re-exchange tokens.
From the tool's definition Closes a running DCA bot with settlement of remaining assets in specified token types (BIT, base tokens, or quote tokens).
Documented attack patterns abuse exactly the kind of access closeDCABot 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 closeDCABot:
{
"version": "1",
"default": "deny",
"tools": {
"closeDCABot": {
"limits": [
{
"counter": "closedcabot_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}closeDCABot 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.
Free to start. No card required.
Closes a running DCA bot. You must specify a close_mode to determine\nhow remaining assets are settled:\n- 1 (DCA_BIT_MODE): settle in BIT\n- 2 (DCA_BASE_MODE): convert all to base tokens\n- 3 (DCA_QUOTE_MODE): convert all to quote token\n\nThe bot must be in a closeable state. Bots that are currently in the\nmiddle of an investment cycle may not be closeable (status_code=503).\n\nRate limit: 3 qps per UID.\n\nAgent hint: Use close_mode=3 (DCA_QUOTE_MODE) if the user wants to convert\neverything back to the quote coin (e.g., USDT). It is categorised as a Write tool in the Bybit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for closeDCABot: 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.
closeDCABot 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 closeDCABot 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 closeDCABot. 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.
closeDCABot 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.