getSpreadTradeHistory

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/getspreadtradehistory.md

WHAT IT DOES

What getSpreadTradeHistory does on Bybit MCP Server

AI agents call getSpreadTradeHistory 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 getSpreadTradeHistory is rated Low

The tool retrieves past transaction data from the Bybit exchange for auditing and review purposes. There are no side effects, no code execution, no data modification or deletion, and no financial movements. It is a straightforward historical data query, consistent with the Read category.

From the tool's definition Tool name and description indicate it 'Query[s] spread trading execution (trade) history' and 'Review fills and execution prices for completed spread trades' — these are read-only operations that retrieve historical data without modifying, deleting, or…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getSpreadTradeHistory 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 getSpreadTradeHistory, this is the rule to start with:

getSpreadTradeHistory Allowed

getSpreadTradeHistory 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": {
    "getSpreadTradeHistory": {}
  }
}

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 getSpreadTradeHistory call is checked against it from then on.

FAQ

Questions about getSpreadTradeHistory

What does the getSpreadTradeHistory tool do? +

Query spread trading execution (trade) history, including individual leg execution details.\n\nUsage Scenarios:\n- Review fills and execution prices for completed spread trades.\n- Audit fees per leg (use. 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 getSpreadTradeHistory? +

Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getSpreadTradeHistory: 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 getSpreadTradeHistory? +

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

Can I rate-limit getSpreadTradeHistory? +

Yes. Add a rate_limit block to the getSpreadTradeHistory 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 getSpreadTradeHistory completely? +

Set action: deny in the PolicyLayer policy for getSpreadTradeHistory. 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 getSpreadTradeHistory? +

getSpreadTradeHistory 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 →