BinanceGetSpotRebateHistoryRecords
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).
This record as markdown: /tools/nirholas-binance-mcp/binancegetspotrebatehistoryrecords.md
What BinanceGetSpotRebateHistoryRecords does on Binance MCP Server
AI agents call BinanceGetSpotRebateHistoryRecords to retrieve information from Binance MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why BinanceGetSpotRebateHistoryRecords is rated Low
This tool retrieves financial transaction history (rebate and commission records) without creating, modifying, or executing any changes. While the data is financial in nature, the tool itself performs only read operations. Medium severity is appropriate because unauthorized access to rebate history could expose financial details and transaction patterns, but the tool cannot move funds or modify accounts.
From the tool's definition The tool description states it 'Retrieve[s] the history of spot rebate records' with no modification or action capability. The verb 'retrieve' and scope limited to historical data access confirms read-only behavior.
Attacks that exploit this kind of access
The rule that runs BinanceGetSpotRebateHistoryRecords safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For BinanceGetSpotRebateHistoryRecords, this is the rule to start with:
BinanceGetSpotRebateHistoryRecords is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceGetSpotRebateHistoryRecords call is checked against it from then on.
Questions about BinanceGetSpotRebateHistoryRecords
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 (nirholas/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue