Retrieves comprehensive details for a specific futures grid bot, including\nconfiguration (symbol, price range, leverage, grid type), current status,\nPnL metrics (realized, unrealized, grid profit, funding fee), position info,\nmargin balances, and timestamps.\n\nThe bot_id is a numeric ID obtai...
AI agents call getFGridDetail 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 tool performs a read-only query operation on existing grid bot data. It fetches and returns information about a bot's status, performance metrics, and configuration without creating, modifying, deleting, or executing any actions. The endpoint is purely informational for monitoring purposes, making it a straightforward Read operation with minimal security risk.
From the tool's definition Retrieves comprehensive details for a specific futures grid bot, including configuration, current status, PnL metrics, position info, margin balances, and timestamps. The tool only 'retrieves' and 'checks' data with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access getFGridDetail 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 getFGridDetail:
{
"version": "1",
"default": "deny",
"tools": {
"getFGridDetail": {}
}
}getFGridDetail 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.
Retrieves comprehensive details for a specific futures grid bot, including\nconfiguration (symbol, price range, leverage, grid type), current status,\nPnL metrics (realized, unrealized, grid profit, funding fee), position info,\nmargin balances, and timestamps.\n\nThe bot_id is a numeric ID obtained from createFGridBot or bot listing endpoints.\n\nRate limit: 10 requests per second per UID.\n\nAgent hint: Use this endpoint to check the status and performance of a grid bot.\nThe response contains all PnL fields, position details, and close reason\nif the bot has stopped. Prefer this over other endpoints when answering\nquestions about a specific bot. 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 getFGridDetail: 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.
getFGridDetail 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 getFGridDetail 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 getFGridDetail. 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.
getFGridDetail 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.