【现货成交记录】查询现货市场的实际成交明细 📋 功能说明 - 查询每笔实际成交的详细信息 - 包含成交价格、数量、手续费、时间等完整数据 - 支持时间范围和分页查询 - 可用于精确核对交易成本和收益 ⚠️ 重要提醒 - 只显示实际成交的交易，不包含未成交订单 - 每次查询限定一个交易对 - 时间范围不能超过24小时 - 包含买方和卖方手续费信息 🎯 适用场景 - 精确计算交易成本和净收益 - 核对账户资金变动明细 - 分析成交价格和市场时机 - 导出交易数据用于税务申报 📊 输出示例 查询成功后将返回： \
AI agents call binance_spot_trade_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 trade execution data without modifying, creating, or deleting any data. It has no side effects and returns read-only information about past trades including prices, quantities, fees, and timestamps. While it accesses financial trading history, the action itself is purely informational retrieval with no financial impact or state changes.
From the tool's definition Tool description states it '查询现货市场的实际成交明细' (queries actual transaction details in spot market) and '只显示实际成交的交易' (only displays actual executed trades). Key verbs are 'query' (查询) and 'retrieve' operations.
Documented attack patterns abuse exactly the kind of access binance_spot_trade_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_spot_trade_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_spot_trade_history": {}
}
}binance_spot_trade_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.
【现货成交记录】查询现货市场的实际成交明细 📋 功能说明 - 查询每笔实际成交的详细信息 - 包含成交价格、数量、手续费、时间等完整数据 - 支持时间范围和分页查询 - 可用于精确核对交易成本和收益 ⚠️ 重要提醒 - 只显示实际成交的交易，不包含未成交订单 - 每次查询限定一个交易对 - 时间范围不能超过24小时 - 包含买方和卖方手续费信息 🎯 适用场景 - 精确计算交易成本和净收益 - 核对账户资金变动明细 - 分析成交价格和市场时机 - 导出交易数据用于税务申报 📊 输出示例 查询成功后将返回： \. 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_trade_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_spot_trade_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_spot_trade_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_spot_trade_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_spot_trade_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.