BinanceGetBoostRewardsHistory
Get Boost Rewards History API allows users to retrieve their boost rewards history for staking activities. This includes the amount of rewards received, the token type (e.g., SOL), and the status of the rewards (e.g., CLAIM or DISTRIBUTE).
This record as markdown: /tools/nirholas-binance-mcp/binancegetboostrewardshistory.md
What BinanceGetBoostRewardsHistory does on Binance MCP Server
AI agents call BinanceGetBoostRewardsHistory 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 BinanceGetBoostRewardsHistory is rated Low
This tool only queries historical staking reward data. Retrieving reward history has no side effects and cannot modify account state, execute trades, or move funds. It is a read-only information lookup operation. The low severity reflects that misuse (e.g., an agent repeatedly querying this endpoint) poses minimal risk—no financial loss or data corruption can result.
From the tool's definition Tool description states it 'retrieve[s] their boost rewards history' with no mention of modifications, deletions, or financial transactions. The operation is purely informational: 'amount of rewards received, the token type, and the status of the rewards.'
Attacks that exploit this kind of access
The rule that runs BinanceGetBoostRewardsHistory 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 BinanceGetBoostRewardsHistory, this is the rule to start with:
BinanceGetBoostRewardsHistory 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 BinanceGetBoostRewardsHistory call is checked against it from then on.
Questions about BinanceGetBoostRewardsHistory
Get Boost Rewards History API allows users to retrieve their boost rewards history for staking activities. This includes the amount of rewards received, the token type (e.g., SOL), and the status of the rewards (e.g., CLAIM or DISTRIBUTE). 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 BinanceGetBoostRewardsHistory: 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.
BinanceGetBoostRewardsHistory 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 BinanceGetBoostRewardsHistory 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 BinanceGetBoostRewardsHistory. 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.
BinanceGetBoostRewardsHistory 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