# get_open_orders

Get open orders for a symbol.

Agent View of the PolicyLayer registry record for `get_open_orders`. HTML page: https://policylayer.com/tools/mixuechu-binance-mcp/get-open-orders

## Facts

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

## Why get_open_orders is rated Low

This tool queries existing order data without creating, modifying, deleting, or executing any trades. It has no side effects and presents minimal risk as it only exposes information the authenticated user already has access to. The low severity reflects that misuse would only expose account data the user already knows, not trigger financial transactions or destructive operations.

From the tool's own definition: "Tool name 'get_open_orders' and description 'Get open orders for a symbol' indicate a retrieval operation. The verb 'get' and the read-only nature of querying existing orders without modification or execution confirm this is a data retrieval action."

## Use case

AI agents call get_open_orders to retrieve information from Binance MCP Server 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 Binance MCP Server:

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

## Other tools on Binance MCP Server (7)

- `cancel_order` — Destructive — https://policylayer.com/tools/mixuechu-binance-mcp/cancel-order.md
- `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_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