Get a list of all sub-accounts. Filter by email or status (enabled/disabled).
AI agents call binance_us_subaccount_list to retrieve information from Binance US MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries sub-account information without creating, modifying, deleting, or executing operations. It is clearly a Read operation. Severity is medium rather than low because exposure of sub-account lists could enable account enumeration attacks or social engineering, though it does not directly move funds or cause destructive damage.
From the tool's definition Tool description states 'Get a list of all sub-accounts' with filtering by email or status. Uses verb 'Get' which retrieves data without modification. However, the sensitive nature of sub-account information in a financial exchange context elevates severity.
Documented attack patterns abuse exactly the kind of access binance_us_subaccount_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance US MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_subaccount_list:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_subaccount_list": {}
}
}binance_us_subaccount_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a list of all sub-accounts. Filter by email or status (enabled/disabled). It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_subaccount_list: 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 US MCP Server. Nothing to install.
binance_us_subaccount_list 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 binance_us_subaccount_list 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 binance_us_subaccount_list. 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.
binance_us_subaccount_list is provided by the Binance US MCP Server MCP server (nirholas/binance-us-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance US MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Binance US MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.