binance_us_staking_rewards
Get staking rewards history for assets on Binance.US. Returns a history of staking rewards earned over time. Response includes: - total: Total number of reward records - data: Array of reward records Each reward record contains: - asset: The reward asset - amount: Reward amount - usdValue: USD va...
This record as markdown: /tools/nirholas-binance-us-mcp/binance-us-staking-rewards.md
What binance_us_staking_rewards does on Binance US MCP Server
AI agents call binance_us_staking_rewards to retrieve information from Binance US 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 binance_us_staking_rewards is rated Low
This tool retrieves staking reward history, which is a read-only query operation that returns historical financial data without side effects. It does not create orders, execute trades, transfer funds, or modify any account state. While the data has financial relevance (rewards and USD values), the tool itself performs no financial transaction—it only queries existing reward records.
From the tool's definition Tool description states 'Get staking rewards history' and 'Returns a history of staking rewards earned over time.' The response includes historical data retrieval (total, data array with reward records) with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
The rule that runs binance_us_staking_rewards safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Binance US MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binance_us_staking_rewards, this is the rule to start with:
binance_us_staking_rewards 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 US MCP Server, apply this rule, and every binance_us_staking_rewards call is checked against it from then on.
Questions about binance_us_staking_rewards
Get staking rewards history for assets on Binance.US. Returns a history of staking rewards earned over time. Response includes: - total: Total number of reward records - data: Array of reward records Each reward record contains: - asset: The reward asset - amount: Reward amount - usdValue: USD value at time of reward - time: Reward timestamp - tranId: Transaction ID - autoRestaked: Whether the reward was automatically restaked If no asset is specified, returns rewards for all staked assets. It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_staking_rewards: 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 US MCP Server. Nothing to install.
binance_us_staking_rewards 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 binance_us_staking_rewards 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 binance_us_staking_rewards. 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.
binance_us_staking_rewards is provided by the Binance US MCP Server MCP server (nirholas/binance-us-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Binance US MCP Server, and thousands of servers like it.
This server
Across the catalogue