Aggregates asset account and OBU account data, queries conversion history orders by cursor pagination.\n- OpenAPI interface, requires API Key authentication\n- ACL permission: RESOURCE_GROUP_EXCHANGE_HISTORY + PERMISSION_READ_WRITE\n- Rate limit: 600/min for same group\n- Old path: /asset/v2/priv...
AI agents call QueryOrderByPage 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 retrieves historical order data across accounts without modifying any state. While it requires READ_WRITE permission, the actual function is data retrieval ('query', 'aggregates', 'queries'). Historical order queries are purely informational with no side effects on trading positions, balances, or account state.
From the tool's definition Tool performs 'queries conversion history orders by cursor pagination' with 'PERMISSION_READ_WRITE' ACL but the primary operation is retrieval/aggregation of historical order data.
Documented attack patterns abuse exactly the kind of access QueryOrderByPage 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 QueryOrderByPage:
{
"version": "1",
"default": "deny",
"tools": {
"QueryOrderByPage": {}
}
}QueryOrderByPage 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.
Aggregates asset account and OBU account data, queries conversion history orders by cursor pagination.\n- OpenAPI interface, requires API Key authentication\n- ACL permission: RESOURCE_GROUP_EXCHANGE_HISTORY + PERMISSION_READ_WRITE\n- Rate limit: 600/min for same group\n- Old path: /asset/v2/private/exchange/query-exchange-order. 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 QueryOrderByPage: 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.
QueryOrderByPage 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 QueryOrderByPage 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 QueryOrderByPage. 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.
QueryOrderByPage 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.