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 BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns existing sub-account information. It performs no write, deletion, execution, or financial operations. While the data retrieved could be sensitive (account identities and status), the blast radius of misuse is limited to unauthorized enumeration of account information. Classification as Read is appropriate with low severity due to the informational nature of the operation.
From the tool's definition Tool retrieves a list of sub-accounts with optional filtering by email or status; the word 'Get' and 'list' indicate data retrieval with no modifications, deletions, or side effects.
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 BNB Chain MCP, 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 BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain 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 BNB Chain MCP. 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 BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.