Retrieve the history of spot rebate records, including commission rebates and referral kickbacks, for the past 7 days or a custom date range (within 30 days).
AI agents call BinanceGetSpotRebateHistoryRecords to retrieve information from Binance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries financial transaction history. It does not modify account state, execute trades, move funds, or perform destructive actions. While it accesses sensitive financial information (rebate history tied to an account), the severity is low because the exposure is limited to historical data retrieval with no side effects or blast radius for misuse.
From the tool's definition Tool retrieves historical rebate records without modifying data. The description uses 'Retrieve' and specifies a query operation over past data within defined time windows (7 days or 30-day custom range).
Documented attack patterns abuse exactly the kind of access BinanceGetSpotRebateHistoryRecords gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceGetSpotRebateHistoryRecords:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceGetSpotRebateHistoryRecords": {}
}
}BinanceGetSpotRebateHistoryRecords 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.
Retrieve the history of spot rebate records, including commission rebates and referral kickbacks, for the past 7 days or a custom date range (within 30 days). It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for BinanceGetSpotRebateHistoryRecords: 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 MCP Server. Nothing to install.
BinanceGetSpotRebateHistoryRecords 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 BinanceGetSpotRebateHistoryRecords 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 BinanceGetSpotRebateHistoryRecords. 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.
BinanceGetSpotRebateHistoryRecords is provided by the Binance MCP Server MCP server (termix-official/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 160 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
160 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.