Creates a single futures grid trading bot. The bot will automatically\nplace grid orders within the specified price range.\n\nRequired parameters include symbol, grid_mode, price range, grid count,\nleverage, grid type, and initial investment. Optional parameters include\nTP/SL settings, entry pr...
AI agents use createFGridBot to commit financial operations through Bybit MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool deploys an automated futures trading bot on a cryptocurrency exchange with real financial capital. It commits funds (initial investment) to leveraged futures positions and places orders automatically. This directly involves financial obligations and trading activity, making it Financial category. The use of leverage amplifies risk significantly, warranting critical severity.
From the tool's definition Creates a single futures grid trading bot...will automatically place grid orders within the specified price range...Required parameters include symbol, grid_mode, price range, grid count, leverage, grid type, and initial investment
Documented attack patterns abuse exactly the kind of access createFGridBot 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 createFGridBot:
{
"version": "1",
"default": "deny",
"tools": {
"createFGridBot": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to createFGridBot is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Creates a single futures grid trading bot. The bot will automatically\nplace grid orders within the specified price range.\n\nRequired parameters include symbol, grid_mode, price range, grid count,\nleverage, grid type, and initial investment. Optional parameters include\nTP/SL settings, entry price trigger, and trailing stop.\n\nBefore calling this endpoint, use /v5/fgridbot/validate to\nvalidate parameter ranges. The response check_code indicates specific\nvalidation errors if the creation fails.\n\nRate limit: 10 requests per second per UID.\nSubject to compliance wall and KYC verification.\n\nAgent hint: Always call validateFGridInput first to verify parameters are in range.\nIf status_code is non-zero, check the check_code for the specific error.\nThe bot_id in a successful response is needed for subsequent operations\nlike getFGridDetail or closeFGridBot. It is categorised as a Financial tool in the Bybit MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for createFGridBot: 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.
createFGridBot is a Financial 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 createFGridBot 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 createFGridBot. 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.
createFGridBot 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.