Closes a running spot grid bot. You must specify a close_mode to\ndetermine how remaining assets are settled:\n- 1 (BIT_MODE): settle in BIT\n- 2 (BASE_MODE): convert all to base token\n- 3 (QUOTE_MODE): convert all to quote token\n- 4 (BASE_AND_QUOTE_MODE): return assets as-is, no conversion\n\n...
AI agents invoke closeGridBot 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.
Closing a grid bot terminates an active trading strategy and triggers asset conversion/settlement. This is a significant exchange operation with real financial side effects (asset conversion, position liquidation), but it is not a direct payment or trade placement. It falls under Execute as it triggers an external operation on the exchange with outcomes depending on arguments (close_mode).
From the tool's definition Closes a running spot grid bot... The bot must be in a closeable state (NEW or RUNNING)... settle remaining assets... convert all to base/quote token
Documented attack patterns abuse exactly the kind of access closeGridBot 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 closeGridBot:
{
"version": "1",
"default": "deny",
"tools": {
"closeGridBot": {
"limits": [
{
"counter": "closegridbot_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}closeGridBot 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.
Closes a running spot grid bot. You must specify a close_mode to\ndetermine how remaining assets are settled:\n- 1 (BIT_MODE): settle in BIT\n- 2 (BASE_MODE): convert all to base token\n- 3 (QUOTE_MODE): convert all to quote token\n- 4 (BASE_AND_QUOTE_MODE): return assets as-is, no conversion\n\nThe bot must be in a closeable state (NEW or RUNNING). Bots in\nCANCELLING or COMPLETED state cannot be closed again.\n\nRate limit: 3 qps per UID.\n\nAgent hint: Use close_mode=3 (QUOTE_MODE) if the user wants to cash out to\nstablecoin. Use close_mode=4 if the user wants to keep both tokens. 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 closeGridBot: 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.
closeGridBot 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 closeGridBot 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 closeGridBot. 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.
closeGridBot 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.