# get_order_history

Get historical orders

Agent View of the PolicyLayer registry record for `get_order_history`. HTML page: https://policylayer.com/tools/bybit/get-order-history

## Facts

- Tool: `get_order_history`
- Server: Bybit (`bybit-mcp-server`) — https://policylayer.com/tools/bybit.md
- Install: `npx -y bybit-mcp-server`
- Homepage: git+https://github.com/ethancod1ng/bybit-mcp-server.git
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_order_history",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'get_order_history' and description 'Get historical orders' indicate a retrieval operation with no modification or execution capability."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Bybit:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_order_history": {}
  }
}
```

## Other tools on Bybit (10)

- `cancel_all_orders` — Destructive — https://policylayer.com/tools/bybit/cancel-all-orders.md
- `cancel_order` — Destructive — https://policylayer.com/tools/bybit/cancel-order.md
- `place_order` — Financial — https://policylayer.com/tools/bybit/place-order.md
- `get_24hr_ticker` — Read — https://policylayer.com/tools/bybit/get-24hr-ticker.md
- `get_account_info` — Read — https://policylayer.com/tools/bybit/get-account-info.md
- `get_klines` — Read — https://policylayer.com/tools/bybit/get-klines.md
- `get_open_orders` — Read — https://policylayer.com/tools/bybit/get-open-orders.md
- `get_orderbook` — Read — https://policylayer.com/tools/bybit/get-orderbook.md
- `get_price` — Read — https://policylayer.com/tools/bybit/get-price.md
- `get_wallet_balance` — Read — https://policylayer.com/tools/bybit/get-wallet-balance.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=bybit · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/bybit