// MCP TOOL REFERENCE

closeFGridBot

ServerBybit MCP Server
CategoryDestructive

WHAT IT DOES

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.

THE RISK

Critical Risk

Why closeFGridBot needs a policy

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.

Documented attack patterns abuse exactly the kind of access closeFGridBot gives an agent:

POLICY

How to control closeFGridBot

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 closeFGridBot:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "closeFGridBot"
  ]
}

closeFGridBot disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Bybit MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bybit MCP Server tools

Financial removeLiquidity Withdraw funds from a Liquidity Mining pool position.\n\n- Financial confirmQuote Confirm the quote and execute the conversion trade.\n\nImportant:\n- Must confirm within t Financial executePurchase Place a buy order to purchase on-chain tokens with payment tokens.\nReturns an Financial executeQuote Execute (accept) a quote to initiate the multi-leg trade.\nThis endpoint is asynchronous - Financial executeRedeem Place a sell order to redeem on-chain tokens for payment tokens.\nReturns an Financial quickRepayment Execute quick repayment for specified coin Financial accountBorrow Manual borrow for Unified account.\n\nRules:\n- Borrowing via OpenAPI endpoint supports va Financial accountRepay Manually repay the liabilities of Unified account.\n\nRules:\n- If neither

All 326 Bybit MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Bybit MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about closeFGridBot

What does the closeFGridBot tool do? +

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.

How do I enforce a policy on closeFGridBot? +

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.

What risk level is closeFGridBot? +

closeFGridBot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit closeFGridBot? +

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.

How do I block closeFGridBot completely? +

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.

What MCP server provides closeFGridBot? +

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.

Enforce policy on every Bybit MCP Server tool call.

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.

CHECK YOUR STACK →

Free to start. No card required.

326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.