Creates a spot grid bot with the specified trading pair, price range,\ngrid count, and investment amount. Optionally supports entry price,\nstop-loss/take-profit, trailing stop, and grid trailing (auto-shift).\n\nPrerequisites:\n- Call validateGridInput first to ensure parameters are valid.\n- Us...
AI agents use createGridBot 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 creates an automated trading bot on a cryptocurrency exchange that commits real funds to execute trades continuously within a defined price range. It directly involves financial obligations and asset deployment on Bybit, making it a Financial category tool with critical severity since an AI agent misusing it could deploy large sums of money into automated trading strategies without proper oversight.
From the tool's definition Creates a spot grid bot with the specified trading pair, price range, grid count, and investment amount. Optionally supports entry price, stop-loss/take-profit, trailing stop, and grid trailing (auto-shift).
Documented attack patterns abuse exactly the kind of access createGridBot 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 createGridBot:
{
"version": "1",
"default": "deny",
"tools": {
"createGridBot": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to createGridBot is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Creates a spot grid bot with the specified trading pair, price range,\ngrid count, and investment amount. Optionally supports entry price,\nstop-loss/take-profit, trailing stop, and grid trailing (auto-shift).\n\nPrerequisites:\n- Call validateGridInput first to ensure parameters are valid.\n- User must be authenticated and pass KYC/compliance checks.\n\nReturns grid_id on success. If the user is banned (status_code=421),\nban_reason_text provides a localized explanation.\n\nRate limit: 3 qps per UID.\n\nAgent hint: Always call validateGridInput before this endpoint. The symbol field\nuses uppercase format like \. 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 createGridBot: 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.
createGridBot 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 createGridBot 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 createGridBot. 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.
createGridBot 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.