Get account balances for all non-zero assets. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY.
AI agents call binance_get_account to retrieve information from Agenti 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 account balance data without creating, modifying, deleting, or executing any operations. Although it accesses sensitive financial account information (requiring API credentials), the read-only nature and absence of side effects place it in the Read category.
From the tool's definition Tool retrieves account balances for non-zero assets with no modification capability. The description explicitly states 'Get account balances' which is a read-only query operation.
Documented attack patterns abuse exactly the kind of access binance_get_account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_get_account:
{
"version": "1",
"default": "deny",
"tools": {
"binance_get_account": {}
}
}binance_get_account 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 account balances for all non-zero assets. Requires BINANCE_API_KEY + BINANCE_SECRET_KEY. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti MCP server in PolicyLayer and add a rule for binance_get_account: 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 Agenti. Nothing to install.
binance_get_account 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_get_account 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_get_account. 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_get_account is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.