Get status list of sub-accounts including activation status and enabled features.
AI agents call binance_us_subaccount_status 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 queries and retrieves sub-account status information with no side effects. It does not create, modify, delete, or execute any operations. The data returned is read-only account metadata. In the context of a financial/trading platform, access to account status information carries low risk when properly scoped — it reveals account state but does not enable unauthorized transactions or fund transfers.
From the tool's definition Tool name indicates 'get status' and description explicitly states 'Get status list of sub-accounts including activation status and enabled features' — purely retrieves information without modification or execution of operations.
Documented attack patterns abuse exactly the kind of access binance_us_subaccount_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_subaccount_status": {}
}
}binance_us_subaccount_status 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 status list of sub-accounts including activation status and enabled features. 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_status: 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_status 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_status 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_status. 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_status 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.