Creates a futures combo trading bot that manages a portfolio of multiple\nfutures symbols. The bot automatically rebalances positions based on the\nconfigured trigger mode (time-based, percentage-based, or both).\n\nRequired parameters include leverage, initial margin, rebalancing mode,\nand at l...
AI agents invoke createComboBot to trigger actions in Bybit MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool deploys an automated trading bot on a cryptocurrency exchange that actively manages futures positions. While it involves financial instruments, it is primarily an execution/automation action rather than a direct financial transaction. However, the bot can autonomously rebalance positions, which carries significant financial risk.
From the tool's definition Creates a futures combo trading bot that manages a portfolio of multiple futures symbols. The bot automatically rebalances positions based on the configured trigger mode (time-based, percentage-based, or both).
Documented attack patterns abuse exactly the kind of access createComboBot 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 createComboBot:
{
"version": "1",
"default": "deny",
"tools": {
"createComboBot": {
"limits": [
{
"counter": "createcombobot_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}createComboBot stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates a futures combo trading bot that manages a portfolio of multiple\nfutures symbols. The bot automatically rebalances positions based on the\nconfigured trigger mode (time-based, percentage-based, or both).\n\nRequired parameters include leverage, initial margin, rebalancing mode,\nand at least one symbol setting with target position percentage and side.\n\nBefore calling this endpoint, use /v5/fcombobot/getlimit to\nvalidate parameter ranges. The response bot_id is needed for subsequent\noperations like getComboDetail or closeComboBot.\n\nRate limit: 10 requests per second per UID.\nSubject to compliance wall, GEO IP check, and KYC verification.\n\nAgent hint: Always call getComboLimit first to verify parameters are in range.\nThe symbol_settings array must contain at least one entry with symbol,\ntarget_position_percent, and side. The bot_id in a successful response\nis needed for getComboDetail and closeComboBot. It is categorised as a Execute tool in the Bybit MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for createComboBot: 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.
createComboBot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the createComboBot 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 createComboBot. 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.
createComboBot 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.