# get_withdraw_history

Get the withdrawal history for the user's Binance account.

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

## Facts

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

## Why get_withdraw_history is rated Low

This tool queries historical withdrawal data without modifying, deleting, or executing any operations. It is a retrieval operation (Read category). However, severity is medium rather than low because withdrawal history reveals sensitive financial information including transaction amounts, timing, and destination addresses, which could be misused if exposed to an untrusted agent to profile user financial behavior or…

From the tool's own definition: "Tool name: 'get_withdraw_history'; description states it retrieves 'withdrawal history' from the user's account—a read-only query operation with no side effects."

## Use case

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

## 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_order_book` — Read — https://policylayer.com/tools/analyticace-binance-mcp-server/get-order-book.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

## 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