Retrieves comprehensive details of a spot grid bot including symbol,\nprice range, investment amount, profit metrics (total profit, grid\nprofit, APR), arbitrage count, status, stop-loss/take-profit settings,\ntrailing stop configuration, and close reason (if closed).\n\nUse this when you need to...
AI agents call queryGridDetail 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 only reads and retrieves data about an existing grid bot configuration and performance metrics. It does not create, modify, delete, or execute any trading operations. The description contains no language indicating state changes, fund movement, or irreversible actions. It is a pure data retrieval operation, fitting the 'Read' category.
From the tool's definition Tool name 'queryGridDetail' and description explicitly states it 'Retrieves comprehensive details' and 'check the current state, performance, or configuration' — purely informational queries with no side effects.
Documented attack patterns abuse exactly the kind of access queryGridDetail 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 queryGridDetail:
{
"version": "1",
"default": "deny",
"tools": {
"queryGridDetail": {}
}
}queryGridDetail 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 of a spot grid bot including symbol,\nprice range, investment amount, profit metrics (total profit, grid\nprofit, APR), arbitrage count, status, stop-loss/take-profit settings,\ntrailing stop configuration, and close reason (if closed).\n\nUse this when you need to check the current state, performance, or\nconfiguration of a specific grid bot. The grid_id is obtained from\ncreateGridBot response or grid list queries.\n\nRate limit: 10 qps per UID.\n\nAgent hint: Use this to answer questions about a specific grid 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 queryGridDetail: 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.
queryGridDetail 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 queryGridDetail 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 queryGridDetail. 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.
queryGridDetail 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.