AI agents call get_account_info to retrieve information from Binance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account information and balance data without modifying any state—it is a pure read operation. However, the data returned is highly sensitive (account balances, holdings) in a financial context, making it high severity due to the risk of information disclosure and potential misuse of financial account details by a compromised agent.
From the tool's definition Tool name is 'get_account_info' and description translates to 'Get account information and balance'. The verb 'get' and the informational nature of retrieving account details indicate a read operation.
Documented attack patterns abuse exactly the kind of access get_account_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance, and nothing reaches the server without passing your rules. This is the rule we recommend for get_account_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_account_info": {}
}
}get_account_info 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.
获取账户信息和余额. It is categorised as a Read tool in the Binance MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP server in PolicyLayer and add a rule for get_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 Binance. Nothing to install.
get_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 get_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 get_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.
get_account_info is provided by the Binance MCP server (binance-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binance, 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.
10 Binance tools catalogued and risk-classified — across an index of 43,000+ MCP servers.