# binance_us_cust_cancel_oco

Cancel an entire OCO (One-Cancels-the-Other) order list. ⚠️ REQUIRES CUSTODIAL SOLUTION API KEY This cancels both legs of the OCO order. Response includes orderListId, orders array, and orderReports with canceled order details.

Agent View of the PolicyLayer registry record for `binance_us_cust_cancel_oco`. HTML page: https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-cancel-oco

## Facts

- Tool: `binance_us_cust_cancel_oco`
- Server: Binance US MCP Server (`nirholas/binance-us-mcp`) — https://policylayer.com/tools/nirholas-binance-us-mcp.md
- Homepage: https://github.com/nirholas/Binance-US-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": "binance_us_cust_cancel_oco",
    "arguments": {}
  }
}
```

## Why binance_us_cust_cancel_oco is rated Critical

This tool irreversibly cancels both legs of an OCO order on a live cryptocurrency exchange. While a cancelled order can theoretically be re-placed, the act of cancellation itself is a one-way, irreversible action — the original order state cannot be restored. This is analogous to a delete operation on financial orders.

From the tool's own definition: "Cancel an entire OCO (One-Cancels-the-Other) order list. This cancels both legs of the OCO order."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

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

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

## Other tools on Binance US MCP Server (92)

- `binance_us_cancel_all_open_orders` — Destructive — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cancel-all-open-orders.md
- `binance_us_cancel_oco` — Destructive — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cancel-oco.md
- `binance_us_cancel_order` — Destructive — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cancel-order.md
- `binance_us_cust_cancel_order` — Destructive — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-cancel-order.md
- `binance_us_cust_cancel_orders_symbol` — Destructive — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-cancel-orders-symbol.md
- `binance_us_cancel_replace` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cancel-replace.md
- `binance_us_cl_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cl-transfer.md
- `binance_us_cust_new_order` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-new-order.md
- `binance_us_cust_oco_order` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-oco-order.md
- `binance_us_cust_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-transfer.md
- `binance_us_cust_undo_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-undo-transfer.md
- `binance_us_cust_wallet_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-cust-wallet-transfer.md
- `binance_us_custodial_custodian_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-custodial-custodian-transfer.md
- `binance_us_custodial_settlement` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-custodial-settlement.md
- `binance_us_custodial_undo_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-custodial-undo-transfer.md
- `binance_us_custodial_wallet_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-custodial-wallet-transfer.md
- `binance_us_new_oco` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-new-oco.md
- `binance_us_new_order` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-new-order.md
- `binance_us_otc_place_order` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-otc-place-order.md
- `binance_us_staking_stake` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-staking-stake.md
- `binance_us_staking_unstake` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-staking-unstake.md
- `binance_us_subaccount_transfer` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-subaccount-transfer.md
- `binance_us_withdraw_crypto` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-withdraw-crypto.md
- `binance_us_withdraw_fiat` — Financial — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-withdraw-fiat.md
- `binance_us_account_info` — Read — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-account-info.md
- `binance_us_agg_trades` — Read — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-agg-trades.md
- `binance_us_all_oco_orders` — Read — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-all-oco-orders.md
- `binance_us_all_orders` — Read — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-all-orders.md
- `binance_us_asset_config` — Read — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-asset-config.md
- `binance_us_avg_price` — Read — https://policylayer.com/tools/nirholas-binance-us-mcp/binance-us-avg-price.md
- …and 62 more: https://policylayer.com/tools/nirholas-binance-us-mcp.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=nirholas-binance-us-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/nirholas-binance-us-mcp