Get older market historical trades for a COIN-M Futures symbol. Requires API key.
AI agents call BinanceDeliveryHistoricalTrades to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical trade data from Binance Delivery Futures, which is a passive data query operation. It has no side effects on wallets, balances, or blockchain state. While it accesses financial market data, it does not move money, execute trades, or create financial obligations. The requirement for an API key is for access control, not indicative of write or destructive capabilities.
From the tool's definition Tool description states 'Get older market historical trades' - a retrieval operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access BinanceDeliveryHistoricalTrades gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceDeliveryHistoricalTrades:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceDeliveryHistoricalTrades": {}
}
}BinanceDeliveryHistoricalTrades 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.
Get older market historical trades for a COIN-M Futures symbol. Requires API key. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain MCP server in PolicyLayer and add a rule for BinanceDeliveryHistoricalTrades: 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 BNB Chain MCP. Nothing to install.
BinanceDeliveryHistoricalTrades 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 BinanceDeliveryHistoricalTrades 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 BinanceDeliveryHistoricalTrades. 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.
BinanceDeliveryHistoricalTrades is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.