Query RFQ trade execution history with optional filtering by IDs, trader type, and status.\nSupports cursor-based pagination. Results include detailed per-leg execution information.\n\nField query priority: rfqId > rfqLinkId, quoteId > quoteLinkId.\nThe
AI agents call getTradeHistory 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 trade data from Bybit without modifying, deleting, or executing any transactions. It performs a straightforward query operation with optional filtering and pagination, which is characteristic of Read-category tools. No financial transactions, state changes, or irreversible actions are possible through this interface.
From the tool's definition Tool name 'getTradeHistory' and description 'Query RFQ trade execution history' indicate data retrieval. Keywords 'query' and 'results include detailed per-leg execution information' confirm read-only operations with no side effects.
Documented attack patterns abuse exactly the kind of access getTradeHistory 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 getTradeHistory:
{
"version": "1",
"default": "deny",
"tools": {
"getTradeHistory": {}
}
}getTradeHistory 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 RFQ trade execution history with optional filtering by IDs, trader type, and status.\nSupports cursor-based pagination. Results include detailed per-leg execution information.\n\nField query priority: rfqId > rfqLinkId, quoteId > quoteLinkId.\nThe. 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 getTradeHistory: 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.
getTradeHistory 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 getTradeHistory 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 getTradeHistory. 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.
getTradeHistory 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.