Get account information including balances, commission rates, and trading permissions. Returns all asset balances (free + locked).
AI agents call bn_account_info to retrieve information from Node2flow/binance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
bn_account_info retrieves account metadata and balances without creating, modifying, or deleting any data. It is a pure read operation. Severity is low because while the data is sensitive (personal account state), exposure does not directly enable financial transfers, account compromise, or destructive actions—those require separate write/execute tools like bn_place_order or bn_cancel_order.
From the tool's definition Tool description states 'Get account information including balances, commission rates, and trading permissions' with explicit emphasis on returns ('Returns all asset balances'). These are query operations with no mutation or side effects.
Attacks that exploit this kind of access
Get account information including balances, commission rates, and trading permissions. Returns all asset balances (free + locked). It is categorised as a Read tool in the Node2flow/binance MCP Server, which means it retrieves data without modifying state.
Register the Node2flow/binance MCP server in PolicyLayer and add a rule for bn_account_info: 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 Node2flow/binance. Nothing to install.
bn_account_info 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 bn_account_info 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 bn_account_info. 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.
bn_account_info is provided by the Node2flow/binance MCP server (node2flow-th/binance-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →