Retrieve a list of child orders created by a strategy with detailed execution information.\n\nWhen to use:\n- View all orders spawned by a specific strategy\n- Check why a strategy order was rejected or canceled\n- Analyze execution prices and timing of strategy orders\n- Monitor real-time order ...
AI agents call queryStrategyOrderList 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 retrieves and queries existing strategy order data from the Bybit exchange. It has no side effects, does not create, modify, delete, or execute trades. While the server as a whole includes financial tools (trading, payments), this specific tool is a read-only query operation with minimal blast radius if misused by an agent — it can only expose order history and status information already visible to…
From the tool's definition Tool name 'queryStrategyOrderList' and description states 'Retrieve a list of child orders' — purely a retrieval operation.
Documented attack patterns abuse exactly the kind of access queryStrategyOrderList 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 queryStrategyOrderList:
{
"version": "1",
"default": "deny",
"tools": {
"queryStrategyOrderList": {}
}
}queryStrategyOrderList 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.
Retrieve a list of child orders created by a strategy with detailed execution information.\n\nWhen to use:\n- View all orders spawned by a specific strategy\n- Check why a strategy order was rejected or canceled\n- Analyze execution prices and timing of strategy orders\n- Monitor real-time order status during strategy execution\n- Debug strategy execution issues\n\nOrder Status Values:\n- 1: Created - Order placed but not yet filled\n- 2: PartiallyFilled - Order partially executed\n- 3: Filled - Order fully executed\n- 4: Cancelled - Order was canceled\n- 5: Rejected - Order rejected by exchange\n\nImportant notes:\n- strategyId is REQUIRED - must provide the parent strategy ID\n- Orders are sorted by creation time (newest first)\n- Use pagination for strategies with many orders\n- Maximum pageSize: 50, default: 20\n- Error codes in response indicate order rejection reasons\n- parentOrderId links replacement orders in chase strategies\n\nAgent hint: Use this endpoint when user wants to see individual orders created by a strategy.\nCommon queries: \. 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 queryStrategyOrderList: 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.
queryStrategyOrderList 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 queryStrategyOrderList 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 queryStrategyOrderList. 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.
queryStrategyOrderList 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.