This record as markdown: /tools/bybit/get-order-history.md
What get_order_history does on Bybit
AI agents call get_order_history to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_order_history is rated Low
This tool queries and retrieves past order data without any side effects. It does not modify, cancel, place, or execute any trades. While it provides financial/trading information, the action itself is purely read-only data retrieval. The low severity reflects that exposure of this tool poses minimal risk to an AI agent—reading historical order data cannot directly cause financial loss or unwanted transactions.
From the tool's definition Tool name 'get_order_history' and description 'Get historical orders' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs get_order_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_order_history, this is the rule to start with:
get_order_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit, apply this rule, and every get_order_history call is checked against it from then on.
Questions about get_order_history
Get historical orders. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_order_history: 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. Nothing to install.
get_order_history 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 get_order_history 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 get_order_history. 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.
get_order_history is provided by the Bybit MCP server (bybit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit, and thousands of servers like it.
This server
Across the catalogue