🚀 合约持仓查询 - 仓位风险实时监控 🔍 功能说明： 查询合约账户的持仓信息，包括持仓数量、入场价格、标记价格、未实现盈亏、强平价格、杠杆倍数等关键数据。支持查询特定合约或所有持仓，提供完整的风险评估信息。 ⚠️ 重要提醒： • 强平风险：当价格接近强平价时会被强制平仓，造成损失 • 实时标记：基于标记价格计算盈亏，与最新成交价可能有差异 • 杠杆风险：高杠杆会放大盈亏，需严格控制仓位规模 • 资金费率：持仓需要支付或收取资金费用，每8小时结算 🎯 适用场景： • 合约交易者监控持仓状态和风险水平 • 风控系统实时评估持仓风险和强平预警 • 交易策略验证和仓位管理优化 • 投资组...
AI agents call binance_futures_positions 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 as it retrieves and queries existing position data from the Binance futures account without modifying state. Severity is medium rather than low because while it only reads data, the information exposed (liquidation prices, leverage, unrealized P&L) could enable an AI agent to make decisions that lead to financial harm if the agent misuses this data in subsequent trading operations.
From the tool's definition Tool description states '查询合约账户的持仓信息' (query futures account position information) and 'support querying specific contracts or all positions.' The function retrieves position data including quantity, entry price, mark price, unrealized P&L, liquidation price,…
Documented attack patterns abuse exactly the kind of access binance_futures_positions 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_futures_positions:
{
"version": "1",
"default": "deny",
"tools": {
"binance_futures_positions": {}
}
}binance_futures_positions 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.
🚀 合约持仓查询 - 仓位风险实时监控 🔍 功能说明： 查询合约账户的持仓信息，包括持仓数量、入场价格、标记价格、未实现盈亏、强平价格、杠杆倍数等关键数据。支持查询特定合约或所有持仓，提供完整的风险评估信息。 ⚠️ 重要提醒： • 强平风险：当价格接近强平价时会被强制平仓，造成损失 • 实时标记：基于标记价格计算盈亏，与最新成交价可能有差异 • 杠杆风险：高杠杆会放大盈亏，需严格控制仓位规模 • 资金费率：持仓需要支付或收取资金费用，每8小时结算 🎯 适用场景： • 合约交易者监控持仓状态和风险水平 • 风控系统实时评估持仓风险和强平预警 • 交易策略验证和仓位管理优化 • 投资组合分析和风险敞口统计 📊 输出示例： 查询成功后将返回： \. 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_futures_positions: 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_futures_positions 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_futures_positions 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_futures_positions. 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_futures_positions 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.