closeFGridBot
Closes (stops) a running futures grid trading bot. The bot will cancel\nall pending grid orders and close positions.\n\nThe bot_id can be obtained from the createFGridBot response or from\ngetFGridDetail. Only bots in a running state can be closed.\n\nRate limit: 10 requests per second per UID.\n...
This record as markdown: /tools/bybit-exchange-trading-mcp/closefgridbot.md
What closeFGridBot does on Bybit MCP Server
AI agents call closeFGridBot 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 closeFGridBot is rated Critical
Closing a grid bot cancels all pending orders and closes open positions — these are irreversible market actions that cannot be undone. Closing positions especially has permanent financial consequences (realizing P&L, removing exposure), making this effectively destructive in nature with high blast radius if triggered unintentionally.
From the tool's definition Closes (stops) a running futures grid trading bot. The bot will cancel all pending grid orders and close positions.
Attacks that exploit this kind of access
The rule that runs closeFGridBot 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 closeFGridBot, this is the rule to start with:
closeFGridBot 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 closeFGridBot call is checked against it from then on.
Questions about closeFGridBot
Closes (stops) a running futures grid trading bot. The bot will cancel\nall pending grid orders and close positions.\n\nThe bot_id can be obtained from the createFGridBot response or from\ngetFGridDetail. 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 grid bot. The bot_id is required and can be\nfound in the createFGridBot response. After closing, use getFGridDetail\nto check the final 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 closeFGridBot: 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.
closeFGridBot 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 closeFGridBot 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 closeFGridBot. 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.
closeFGridBot 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