🏦 统一账户总览 - Portfolio Margin 全资产管理 🔍 功能说明： 获取统一账户（Portfolio Margin）的完整信息，包括总保证金、可用余额、未实现盈亏、各币种资产分布、保证金使用率等核心数据。提供跨现货和合约的全局资产视角。 ⚠️ 重要提醒： • 保证金模式：统一账户支持跨品种保证金共享，风险更集中 • 强平风险：保证金不足时可能触发全账户强制平仓 • 计算复杂：涉及现货、合约、期权等多种资产的综合评估 • 实时变动：盈亏和保证金状态随市价实时变动 🎯 适用场景： • 专业交易者查看整体资产配置和风险状况 • Portfolio Margin用户监控保证...
AI agents call binance_portfolio_account 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 is a Read operation—it queries account data without side effects. However, severity is high because the retrieved data (margin ratios, liquidation risk, positions across spot and futures) is highly sensitive and could directly inform destructive or financial decisions by an AI agent (e.g., an agent could misinterpret margin usage and trigger forced liquidation by making additional trades, or use this data to…
From the tool's definition Tool description states it 'retrieves' (获取) complete Portfolio Margin account information including total margin, available balance, unrealized P&L, asset distribution, and margin usage rate. Function is 'get' based: 获取统一账户（Portfolio Margin）的完整信息.
Documented attack patterns abuse exactly the kind of access binance_portfolio_account 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_portfolio_account:
{
"version": "1",
"default": "deny",
"tools": {
"binance_portfolio_account": {}
}
}binance_portfolio_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.
🏦 统一账户总览 - Portfolio Margin 全资产管理 🔍 功能说明： 获取统一账户（Portfolio Margin）的完整信息，包括总保证金、可用余额、未实现盈亏、各币种资产分布、保证金使用率等核心数据。提供跨现货和合约的全局资产视角。 ⚠️ 重要提醒： • 保证金模式：统一账户支持跨品种保证金共享，风险更集中 • 强平风险：保证金不足时可能触发全账户强制平仓 • 计算复杂：涉及现货、合约、期权等多种资产的综合评估 • 实时变动：盈亏和保证金状态随市价实时变动 🎯 适用场景： • 专业交易者查看整体资产配置和风险状况 • Portfolio Margin用户监控保证金使用率 • 风控系统评估账户整体风险敞口 • 资产配置优化和再平衡决策 🏛️ 输出示例： 查询成功后将返回： \. 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_portfolio_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 Binance. Nothing to install.
binance_portfolio_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_portfolio_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_portfolio_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_portfolio_account 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.