get_deposit_history

Get the deposit history for a specific coin on the user's Binance account.

SERVERBinance MCP Server SOURCEanalyticace/binance-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/analyticace-binance-mcp-server/get-deposit-history.md

WHAT IT DOES

What get_deposit_history does on Binance MCP Server

AI agents call get_deposit_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.

RISK

Why get_deposit_history is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_deposit_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_deposit_history, this is the rule to start with:

get_deposit_history Allowed

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

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every get_deposit_history call is checked against it from then on.

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.

KEEP EXPLORING

More on Binance MCP Server, and thousands of servers like it.

This server

All 15 Binance MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →