# cancel_order

Cancel an existing order (⚠️ WARNING: Affects real orders on mainnet)

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

## Facts

- Tool: `cancel_order`
- 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: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why cancel_order is rated Critical

Canceling an order is an irreversible action that permanently terminates a financial commitment on a live trading exchange. This meets the Destructive category definition (irreversibly deletes or overwrites data / actions that cannot be undone). On a trading platform, a canceled order cannot be restored in its original state.

From the tool's own definition: "Tool name 'cancel_order' and description explicitly states it 'Cancel an existing order' with warning '⚠️ WARNING: Affects real orders on mainnet'. Cancellation of financial orders is irreversible once executed."

## Use case

AI agents call cancel_order to permanently remove resources in Bybit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_order"
  ]
}
```

## Other tools on Bybit (10)

- `cancel_all_orders` — Destructive — https://policylayer.com/tools/bybit/cancel-all-orders.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_order_history` — Read — https://policylayer.com/tools/bybit/get-order-history.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