💰 现货余额查询 - 资产分布详细统计 🔍 功能说明： 查询现货账户中所有币种的余额情况，包括可用余额、冻结余额和总余额。自动过滤余额为0的币种，提供清晰的资产分布概览和资金使用状况。 ⚠️ 重要提醒： • 冻结余额：包含未成交订单占用的资金，不可用于新交易 • 余额精度：显示币种的实际持有精度，小数位数因币种而异 • 实时数据：余额会因交易、转账等操作实时变动 • 估值计算：仅显示数量，如需USD估值请使用价格工具计算 🎯 适用场景： • 投资者查看资产配置和持仓分布 • 交易前确认可用余额是否充足 • 资产管理和投资组合分析 • 审计和对账时核实资产明细 💼 输出示例： 查询...
AI agents call binance_spot_balances 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 balance information without any side effects or modifications. It is a pure data query operation that returns asset details. While it accesses financial account data (warranting 'medium' severity due to sensitive financial information exposure and potential for reconnaissance by a compromised agent), it does not move money, execute trades, delete data, or modify any state.
From the tool's definition Tool name 'binance_spot_balances' and description explicitly state it 'queries' (查询) spot account balances including available balance, frozen balance, and total balance.
Documented attack patterns abuse exactly the kind of access binance_spot_balances 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 binance_spot_balances:
{
"version": "1",
"default": "deny",
"tools": {
"binance_spot_balances": {}
}
}binance_spot_balances 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.
💰 现货余额查询 - 资产分布详细统计 🔍 功能说明： 查询现货账户中所有币种的余额情况，包括可用余额、冻结余额和总余额。自动过滤余额为0的币种，提供清晰的资产分布概览和资金使用状况。 ⚠️ 重要提醒： • 冻结余额：包含未成交订单占用的资金，不可用于新交易 • 余额精度：显示币种的实际持有精度，小数位数因币种而异 • 实时数据：余额会因交易、转账等操作实时变动 • 估值计算：仅显示数量，如需USD估值请使用价格工具计算 🎯 适用场景： • 投资者查看资产配置和持仓分布 • 交易前确认可用余额是否充足 • 资产管理和投资组合分析 • 审计和对账时核实资产明细 💼 输出示例： 查询成功后将返回： \. 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 binance_spot_balances: 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.
binance_spot_balances 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_spot_balances 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_spot_balances. 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_spot_balances is provided by the Binance MCP server (kydlikebtc/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.
35 Binance tools catalogued and risk-classified — across an index of 43,000+ MCP servers.