binance_us_staking_history
Get staking transaction history for assets on Binance.US. Returns a history of staking and unstaking transactions. Response includes for each transaction: - asset: The asset involved - amount: Transaction amount - type: Transaction type (staked, unstaked, etc.) - initiatedTime: Transaction initia...
This record as markdown: /tools/nirholas-binance-mcp/binance-us-staking-history.md
What binance_us_staking_history does on Binance MCP Server
AI agents call binance_us_staking_history 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 binance_us_staking_history is rated Low
This tool purely queries and returns historical information about staking transactions. It does not execute trades, move funds, create/modify records, or perform destructive operations. The response fields are all informational (asset names, amounts, timestamps, statuses) from past transactions. No financial movement occurs during the query itself—it only retrieves data about prior operations.
From the tool's definition Tool retrieves historical staking transaction data (asset, amount, type, timestamp, status) without modifying or deleting records.
Attacks that exploit this kind of access
The rule that runs binance_us_staking_history 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 binance_us_staking_history, this is the rule to start with:
binance_us_staking_history 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 binance_us_staking_history call is checked against it from then on.
Questions about binance_us_staking_history
Get staking transaction history for assets on Binance.US. Returns a history of staking and unstaking transactions. Response includes for each transaction: - asset: The asset involved - amount: Transaction amount - type: Transaction type (staked, unstaked, etc.) - initiatedTime: Transaction initiation timestamp - status: Transaction status (SUCCESS, PENDING, etc.) If no asset is specified, returns history for all assets. 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 binance_us_staking_history: 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.
binance_us_staking_history 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_history 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_history. 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_history 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