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...
AI agents call binance_us_staking_history to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation that queries historical staking transactions from Binance.US. It has no side effects—it cannot create, modify, delete, or execute any transactions. The blast radius of misuse is minimal; an attacker could only view transaction history without affecting user assets or account state. This clearly falls under the Read category.
From the tool's definition Tool retrieves staking transaction history with no capability to modify, delete, or execute transactions. Returns read-only data including asset, amount, type, timestamp, and status.
Documented attack patterns abuse exactly the kind of access binance_us_staking_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for binance_us_staking_history:
{
"version": "1",
"default": "deny",
"tools": {
"binance_us_staking_history": {}
}
}binance_us_staking_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 BNB Chain MCP MCP Server, which means it retrieves data without modifying state.
Register the BNB Chain 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 BNB Chain MCP. 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 BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.