# get_order_book

A read tool on the Binance MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_order_book`. HTML page: https://policylayer.com/tools/analyticace-binance-mcp-server/get-order-book

## Facts

- Tool: `get_order_book`
- Server: Binance MCP Server (`analyticace/binance-mcp-server`) — https://policylayer.com/tools/analyticace-binance-mcp-server.md
- Homepage: https://github.com/AnalyticAce/binance-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, 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_book",
    "arguments": {}
  }
}
```

## Why get_order_book is rated Low

The tool retrieves market data (order book) which is a read operation with no side effects. It does not create, modify, delete, or execute transactions. While the server enables financial operations, this specific tool only accesses publicly available market information. Confidence is slightly reduced due to empty description, but the name and context strongly indicate a read operation.

From the tool's own definition: "Tool name 'get_order_book' indicates retrieval of order book data (market depth information). No description provided, but within the context of a Binance trading server, this is a standard read-only query operation that retrieves current market data without…"

## Use case

AI agents call get_order_book 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_order_book": {}
  }
}
```

## Other tools on Binance MCP Server (14)

- `create_order` — Financial — https://policylayer.com/tools/analyticace-binance-mcp-server/create-order.md
- `get_account_snapshot` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-account-snapshot.md
- `get_available_assets` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-available-assets.md
- `get_balance` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-balance.md
- `get_deposit_address` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-deposit-address.md
- `get_deposit_history` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-deposit-history.md
- `get_fee_info` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-fee-info.md
- `get_liquidation_history` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-liquidation-history.md
- `get_orders` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-orders.md
- `get_pnl` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-pnl.md
- `get_position_info` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-position-info.md
- `get_ticker` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-ticker.md
- `get_ticker_price` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-ticker-price.md
- `get_withdraw_history` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-withdraw-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=analyticace-binance-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/analyticace-binance-mcp-server