Closes (stops) a running futures combo trading bot. The bot will cancel\nall pending orders and close all positions across the portfolio.\n\nThe bot_id can be obtained from the createComboBot response or from\ngetComboDetail. Only bots in a running state can be closed.\n\nRate limit: 10 requests ...
AI agents call closeComboBot to permanently remove resources in Bybit MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly stops a trading bot, cancels all pending orders, and closes all open positions across a portfolio. Closing positions in a live trading environment is effectively irreversible (market conditions change), and mass-closing positions can result in significant financial losses.
From the tool's definition Closes (stops) a running futures combo trading bot. The bot will cancel all pending orders and close all positions across the portfolio.
Documented attack patterns abuse exactly the kind of access closeComboBot 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 closeComboBot:
{
"version": "1",
"default": "deny",
"hide": [
"closeComboBot"
]
}closeComboBot disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Closes (stops) a running futures combo trading bot. The bot will cancel\nall pending orders and close all positions across the portfolio.\n\nThe bot_id can be obtained from the createComboBot response or from\ngetComboDetail. Only bots in a running state can be closed.\n\nRate limit: 10 requests per second per UID.\n\nAgent hint: Use this to stop a running combo bot. The bot_id is required and can be\nfound in the createComboBot response. The stop_type indicates the reason\nfor closing. After closing, use getComboDetail to check the final PnL\nand close reason. It is categorised as a Destructive tool in the Bybit MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for closeComboBot: 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.
closeComboBot is a Destructive 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 closeComboBot 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 closeComboBot. 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.
closeComboBot 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.