getTradeHistory

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/gettradehistory.md

WHAT IT DOES

What getTradeHistory does on Bybit MCP Server

AI agents call getTradeHistory to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getTradeHistory is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getTradeHistory safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getTradeHistory, this is the rule to start with:

getTradeHistory Allowed

getTradeHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTradeHistory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every getTradeHistory call is checked against it from then on.

FAQ

Questions about getTradeHistory

What does the getTradeHistory tool do? +

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.

How do I enforce a policy on getTradeHistory? +

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.

What risk level is getTradeHistory? +

getTradeHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getTradeHistory? +

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.

How do I block getTradeHistory completely? +

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.

What MCP server provides getTradeHistory? +

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.

KEEP EXPLORING

More on Bybit MCP Server, and thousands of servers like it.

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →