BinanceSubAccountGetDepositHistory
Query sub-account deposit history.
This record as markdown: /tools/nirholas-binance-mcp/binancesubaccountgetdeposithistory.md
What BinanceSubAccountGetDepositHistory does on Binance MCP Server
AI agents call BinanceSubAccountGetDepositHistory 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.
Why BinanceSubAccountGetDepositHistory is rated Low
This tool retrieves historical deposit information from a sub-account without creating, modifying, or deleting any data. It is a read-only query operation that has minimal risk if misused, as it only exposes past deposit records. The severity is low because unauthorized access to deposit history could reveal financial activity but does not enable direct financial transactions or destructive operations.
From the tool's definition Tool name contains 'GetDepositHistory' and description states 'Query sub-account deposit history' — both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs BinanceSubAccountGetDepositHistory 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 BinanceSubAccountGetDepositHistory, this is the rule to start with:
BinanceSubAccountGetDepositHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceSubAccountGetDepositHistory call is checked against it from then on.
Questions about BinanceSubAccountGetDepositHistory
Query sub-account deposit history. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for BinanceSubAccountGetDepositHistory: 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.
BinanceSubAccountGetDepositHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the BinanceSubAccountGetDepositHistory 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.
Set action: deny in the PolicyLayer policy for BinanceSubAccountGetDepositHistory. 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.
BinanceSubAccountGetDepositHistory is provided by the Binance MCP Server MCP server (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue