# cancel_order

Cancel a specific order.

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

## Facts

- Tool: `cancel_order`
- Server: Binance MCP Server (`mixuechu/binance-mcp`) — https://policylayer.com/tools/mixuechu-binance-mcp.md
- Homepage: https://github.com/mixuechu/binance-mcp
- 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

Cancelling an order is an irreversible action: the order is permanently removed from the order book and cannot be restored. While it does not move money directly, it destroys a standing financial commitment that cannot be undone, placing it in the Destructive category.

From the tool's own definition: "Cancel a specific order — cancellation of a financial order is irreversible; once cancelled, the order cannot be reinstated."

## Use case

AI agents call cancel_order to permanently remove resources in Binance MCP Server, 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 Binance MCP Server:

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

## Other tools on Binance MCP Server (7)

- `execute_hedge_arbitrage_strategy` — Execute — https://policylayer.com/tools/mixuechu-binance-mcp/execute-hedge-arbitrage-strategy.md
- `find_arbitrage_pairs` — Financial — https://policylayer.com/tools/mixuechu-binance-mcp/find-arbitrage-pairs.md
- `place_market_order` — Financial — https://policylayer.com/tools/mixuechu-binance-mcp/place-market-order.md
- `get_account_balance` — Read — https://policylayer.com/tools/mixuechu-binance-mcp/get-account-balance.md
- `get_funding_rate_history` — Read — https://policylayer.com/tools/mixuechu-binance-mcp/get-funding-rate-history.md
- `get_open_orders` — Read — https://policylayer.com/tools/mixuechu-binance-mcp/get-open-orders.md
- `get_trade_history` — Read — https://policylayer.com/tools/mixuechu-binance-mcp/get-trade-history.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=mixuechu-binance-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mixuechu-binance-mcp