# BinanceCrossMarginAccount

Query Cross Margin account details including balances, margin level, and collateral info.

Agent View of the PolicyLayer registry record for `BinanceCrossMarginAccount`. HTML page: https://policylayer.com/tools/nirholas-binance-mcp/binancecrossmarginaccount

## Facts

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

## Why BinanceCrossMarginAccount is rated Low

This is a read-only operation that queries and retrieves financial account data. While the data is sensitive (crypto asset balances and margin metrics), the tool itself performs no write, execute, or destructive actions.

From the tool's own definition: "Tool name 'Query Cross Margin account details' and description explicitly states it retrieves account information (balances, margin level, collateral info) with no modification or execution capability."

## Use case

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

## Other tools on Binance MCP Server (733)

- `binance_us_cancel_all_open_orders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cancel-all-open-orders.md
- `binance_us_cancel_oco` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cancel-oco.md
- `binance_us_cancel_order` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cancel-order.md
- `binance_us_cancel_replace` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cancel-replace.md
- `binance_us_cust_cancel_oco` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cust-cancel-oco.md
- `binance_us_cust_cancel_order` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cust-cancel-order.md
- `binance_us_cust_cancel_orders_symbol` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binance-us-cust-cancel-orders-symbol.md
- `BinanceCancelHashRateResaleConfiguration` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancecancelhashrateresaleconfiguration.md
- `BinanceConvertCancelLimitOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binanceconvertcancellimitorder.md
- `BinanceCrossMarginCancelAllOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancecrossmargincancelallorders.md
- `BinanceCrossMarginCancelOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancecrossmargincancelorder.md
- `BinanceDeleteOpenOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeleteopenorders.md
- `BinanceDeleteOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeleteorder.md
- `BinanceDeleteUserDataStream` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeleteuserdatastream.md
- `BinanceDeliveryCancelAllOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeliverycancelallorders.md
- `BinanceDeliveryCancelBatchOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeliverycancelbatchorders.md
- `BinanceDeliveryCancelOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeliverycancelorder.md
- `BinanceDeliveryCountdownCancelAll` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedeliverycountdowncancelall.md
- `BinanceDisableIsolatedMarginAccount` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancedisableisolatedmarginaccount.md
- `BinanceFutureCancelAlgoOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturecancelalgoorder.md
- `BinanceFuturesCancelAllOpenOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescancelallopenorders.md
- `BinanceFuturesCancelAllOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescancelallorders.md
- `BinanceFuturesCancelBatchOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescancelbatchorders.md
- `BinanceFuturesCancelOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescancelorder.md
- `BinanceFuturesCOINMCancelAllOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescoinmcancelallorders.md
- `BinanceFuturesCOINMCancelBatchOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescoinmcancelbatchorders.md
- `BinanceFuturesCOINMCancelOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturescoinmcancelorder.md
- `BinanceFuturesUSDMCancelAllOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturesusdmcancelallorders.md
- `BinanceFuturesUSDMCancelBatchOrders` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturesusdmcancelbatchorders.md
- `BinanceFuturesUSDMCancelOrder` — Destructive — https://policylayer.com/tools/nirholas-binance-mcp/binancefuturesusdmcancelorder.md
- …and 703 more: https://policylayer.com/tools/nirholas-binance-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-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/nirholas-binance-mcp