BinanceSubAccountList
Get a list of all sub-accounts under your master account. Returns email, status, and creation time for each sub-account.
This record as markdown: /tools/nirholas-binance-mcp/binancesubaccountlist.md
What BinanceSubAccountList does on Binance MCP Server
AI agents call BinanceSubAccountList 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 BinanceSubAccountList is rated Low
This tool retrieves account metadata (email addresses, status, creation timestamps) for sub-accounts under a master Binance account. While it does not modify data, the exposure of this sub-account enumeration information could enable account reconnaissance or social engineering attacks if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] a list of all sub-accounts' and 'Returns email, status, and creation time' — purely a data retrieval operation with no modifications, deletions, or financial transactions.
Attacks that exploit this kind of access
The rule that runs BinanceSubAccountList 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 BinanceSubAccountList, this is the rule to start with:
BinanceSubAccountList 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 BinanceSubAccountList call is checked against it from then on.
Questions about BinanceSubAccountList
Get a list of all sub-accounts under your master account. Returns email, status, and creation time for each sub-account. 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 BinanceSubAccountList: 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.
BinanceSubAccountList 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 BinanceSubAccountList 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 BinanceSubAccountList. 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.
BinanceSubAccountList 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