# get_trade_history

Get recent trade history for a pair.

Agent View of the PolicyLayer registry record for `get_trade_history`. HTML page: https://policylayer.com/tools/mixuechu-binance-mcp/get-trade-history

## Facts

- Tool: `get_trade_history`
- 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_trade_history",
    "arguments": {}
  }
}
```

## Why get_trade_history is rated Low

This tool retrieves historical trading data for a cryptocurrency pair without modifying, deleting, or executing any transactions. It is a straightforward data query operation with no capability to affect account state, execute trades, or move funds. The low severity reflects minimal risk even if an AI agent calls it with arbitrary arguments, as the worst outcome would be retrieving unintended historical data.

From the tool's own definition: "Tool name 'get_trade_history' and description 'Get recent trade history for a pair' indicate a query/retrieval operation with no side effects. The verb 'Get' and the use of 'history' confirm read-only access to past transaction data."

## Use case

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

## 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_open_orders` — Read — https://policylayer.com/tools/mixuechu-binance-mcp/get-open-orders.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