【合约历史订单】查询合约市场的历史订单记录 📋 功能说明 - 查询所有历史订单：已成交、已取消、被拒绝、已过期 - 支持时间范围筛选（最大7天） - 支持分页查询和数量限制 - 包含订单详细状态、成交信息和实现盈亏 ⚠️ 重要提醒 - 每次查询只能指定一个合约 - 时间范围不能超过7天 - 默认按时间倒序返回（最新的在前） - 数据量大时建议使用limit参数限制 🎯 适用场景 - 查看历史交易记录和盈亏情况 - 分析交易策略效果和成功率 - 核对账户盈亏和手续费 - 导出合约交易数据进行分析 📊 输出示例 查询成功后将返回： \
AI agents call binance_futures_order_history 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 and queries historical order data without side effects. It performs data retrieval only (list, fetch, view past transactions) with no capability to create, modify, delete, or execute trades. The severity is low because misuse would only expose historical transaction information without enabling destructive actions or financial movements.
From the tool's definition Tool description explicitly states '查询合约市场的历史订单记录' (query futures market historical order records) and lists only read operations: 'viewing historical trade records', 'analyzing trading strategy', 'verifying account profit/loss', 'exporting contract trading…
Documented attack patterns abuse exactly the kind of access binance_futures_order_history 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_order_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_futures_order_history": {}
}
}binance_futures_order_history 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.
【合约历史订单】查询合约市场的历史订单记录 📋 功能说明 - 查询所有历史订单：已成交、已取消、被拒绝、已过期 - 支持时间范围筛选（最大7天） - 支持分页查询和数量限制 - 包含订单详细状态、成交信息和实现盈亏 ⚠️ 重要提醒 - 每次查询只能指定一个合约 - 时间范围不能超过7天 - 默认按时间倒序返回（最新的在前） - 数据量大时建议使用limit参数限制 🎯 适用场景 - 查看历史交易记录和盈亏情况 - 分析交易策略效果和成功率 - 核对账户盈亏和手续费 - 导出合约交易数据进行分析 📊 输出示例 查询成功后将返回： \. 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_order_history: 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_order_history 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_order_history 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_order_history. 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_order_history 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.