Validates the input parameters for creating a futures grid bot and returns\nthe allowable ranges for each parameter (investment, profit, grid count,\nprice bounds, leverage, TP/SL, etc.).\n\nUse this endpoint before calling /v5/fgridbot/create to ensure\nparameters are within valid bounds. The re...
AI agents call validateFGridInput to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation: it queries and retrieves validation rules and parameter constraints without modifying any state, creating any orders, or executing trades. It is a pure information-retrieval tool used for input validation prior to other operations. The low severity reflects that misuse causes only informational errors, not financial loss or unintended transactions.
From the tool's definition The tool "validates the input parameters" and "returns the allowable ranges for each parameter". It performs a pre-flight check with no side effects—the description explicitly states it should be called "before calling /v5/fgridbot/create" and only returns…
Documented attack patterns abuse exactly the kind of access validateFGridInput 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 validateFGridInput:
{
"version": "1",
"default": "deny",
"tools": {
"validateFGridInput": {}
}
}validateFGridInput is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validates the input parameters for creating a futures grid bot and returns\nthe allowable ranges for each parameter (investment, profit, grid count,\nprice bounds, leverage, TP/SL, etc.).\n\nUse this endpoint before calling /v5/fgridbot/create to ensure\nparameters are within valid bounds. The response includes a check_code that\nindicates which parameter is out of range if validation fails.\n\nRate limit: 10 requests per second per UID.\n\nAgent hint: Call this endpoint first to get valid parameter ranges before creating a grid bot.\nIf check_code is non-zero, the specific validation error is indicated by the code value. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for validateFGridInput: 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.
validateFGridInput is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validateFGridInput 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 validateFGridInput. 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.
validateFGridInput 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.