get_deposit_history

THE RISK

Low Risk

Why get_deposit_history needs a policy

This tool queries and retrieves past deposit records from the user's account. It has no side effects, does not execute trades, does not move funds, and does not modify any data. It is purely informational, similar to other Read-category tools on the server (get_account_snapshot, get_balance, get_order_book, get_orders).

From the tool's definition Tool name is 'get_deposit_history' and description states 'Get the deposit history for a specific coin on the user's Binance account' — this retrieves historical data without modification.

Documented attack patterns abuse exactly the kind of access get_deposit_history gives an agent:

POLICY

How to control get_deposit_history

PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_deposit_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_deposit_history": {}
  }
}

get_deposit_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Binance MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Binance MCP Server tools

Financial create_order create_order Read get_account_snapshot Get the account snapshot for the user's Binance account. Read get_available_assets Get a list of all available assets and trading pairs on Binance. Read get_balance Get the current account balance for all assets on Binance. Read get_deposit_address Get the deposit address for a specific coin on the user's Binance account. Read get_fee_info get_fee_info Read get_liquidation_history Get the liquidation history on Binance account. Read get_order_book get_order_book

All 15 Binance MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about get_deposit_history

What does the get_deposit_history tool do? +

Get the deposit history for a specific coin on the user's Binance account. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_deposit_history? +

Register the Binance MCP Server MCP server in PolicyLayer and add a rule for get_deposit_history: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Binance MCP Server. Nothing to install.

What risk level is get_deposit_history? +

get_deposit_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_deposit_history? +

Yes. Add a rate_limit block to the get_deposit_history rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block get_deposit_history completely? +

Set action: deny in the PolicyLayer policy for get_deposit_history. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides get_deposit_history? +

get_deposit_history is provided by the Binance MCP Server MCP server (analyticace/binance-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Binance MCP Server tool call.

Start from Binance MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →