Query historical trade records with pagination support.\n\nQuery Parameters:\n- Time range filtering supported\n- Pagination support\n- Maximum 100 records per page\n\nResults are sorted by creation time in descending order (newest first).\n\nUse Cases:\n- Generate trade reports for users\n- Reco...
AI agents call queryTradeHistory 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-only operation that retrieves and filters historical trading data from the user's account. It has no side effects—it does not create, modify, delete, or execute any trades or financial transactions. The use cases (reporting, auditing, exporting) all confirm passive data retrieval.
From the tool's definition Tool name 'queryTradeHistory' and description explicitly states it 'Query historical trade records' with 'pagination support' and retrieves 'trade reports', 'reconciliation', and 'export' use cases.
Documented attack patterns abuse exactly the kind of access queryTradeHistory 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 queryTradeHistory:
{
"version": "1",
"default": "deny",
"tools": {
"queryTradeHistory": {}
}
}queryTradeHistory 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.
Query historical trade records with pagination support.\n\nQuery Parameters:\n- Time range filtering supported\n- Pagination support\n- Maximum 100 records per page\n\nResults are sorted by creation time in descending order (newest first).\n\nUse Cases:\n- Generate trade reports for users\n- Reconciliation and auditing\n- Export trade history for accounting. 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 queryTradeHistory: 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.
queryTradeHistory 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 queryTradeHistory 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 queryTradeHistory. 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.
queryTradeHistory 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.