closeFMartBot
Closes (stops) a running futures Martingale trading bot. The bot will\ncancel all pending orders and close the position.\n\nThe bot_id can be obtained from the createFMartBot response or from\ngetFMartDetail. Only bots in a running state can be closed.\n\nRate limit: 10 requests per second per UI...
This record as markdown: /tools/bybit-exchange-trading-mcp/closefmartbot.md
What closeFMartBot does on Bybit MCP Server
AI agents call closeFMartBot 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.
Why closeFMartBot is rated Critical
This tool irreversibly stops a running trading bot, cancels all its pending orders, and closes open positions. Cancelling orders and force-closing positions cannot be undone — the market exposure is eliminated and any associated trades are finalized.
From the tool's definition Closes (stops) a running futures Martingale trading bot. The bot will cancel all pending orders and close the position.
Attacks that exploit this kind of access
The rule that runs closeFMartBot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For closeFMartBot, this is the rule to start with:
closeFMartBot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every closeFMartBot call is checked against it from then on.
Questions about closeFMartBot
Closes (stops) a running futures Martingale trading bot. The bot will\ncancel all pending orders and close the position.\n\nThe bot_id can be obtained from the createFMartBot response or from\ngetFMartDetail. 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 Martingale bot. The bot_id is required and\ncan be found in the createFMartBot response. The stop_type indicates\nthe reason for closing. After closing, use getFMartDetail to check the\nfinal PnL and 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 closeFMartBot: 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.
closeFMartBot 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 closeFMartBot 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 closeFMartBot. 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.
closeFMartBot 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.
More on Bybit MCP Server, and thousands of servers like it.
Across the catalogue