BinanceGetBnsolRewardsHistory
Get Boost Rewards History API allows users to retrieve their historical boost rewards data for staking, including the amount of rewards, token type (e.g., SOL), and status of the rewards (e.g., CLAIM, DISTRIBUTE).
This record as markdown: /tools/nirholas-binance-mcp/binancegetbnsolrewardshistory.md
What BinanceGetBnsolRewardsHistory does on Binance MCP Server
AI agents call BinanceGetBnsolRewardsHistory 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 BinanceGetBnsolRewardsHistory is rated Low
This tool only queries and returns historical reward information without any side effects. It does not create, modify, delete, or execute any financial transactions. While it operates on a financial platform (Binance), it is purely informational/read-only access to past reward data, making it a Read category tool with low severity risk.
From the tool's definition Tool retrieves historical boost rewards data for staking, including amount, token type, and reward status. Verbs used: 'retrieve', 'Get'. No modification, deletion, or execution of trades/payments occurs.
Attacks that exploit this kind of access
The rule that runs BinanceGetBnsolRewardsHistory 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 BinanceGetBnsolRewardsHistory, this is the rule to start with:
BinanceGetBnsolRewardsHistory 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 BinanceGetBnsolRewardsHistory call is checked against it from then on.
Questions about BinanceGetBnsolRewardsHistory
Get Boost Rewards History API allows users to retrieve their historical boost rewards data for staking, including the amount of rewards, token type (e.g., SOL), and status of the rewards (e.g., CLAIM, 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 BinanceGetBnsolRewardsHistory: 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.
BinanceGetBnsolRewardsHistory 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 BinanceGetBnsolRewardsHistory 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 BinanceGetBnsolRewardsHistory. 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.
BinanceGetBnsolRewardsHistory 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