BinanceGetWbethUnwrapHistory
Get WBETH Unwrap History API allows users to retrieve historical records of WBETH unwrap operations, including asset conversion details, exchange rates, and transaction status.
This record as markdown: /tools/nirholas-binance-mcp/binancegetwbethunwraphistory.md
What BinanceGetWbethUnwrapHistory does on Binance MCP Server
AI agents call BinanceGetWbethUnwrapHistory 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 BinanceGetWbethUnwrapHistory is rated Low
This tool queries past transaction history without modifying, executing operations, or affecting financial state. It is informational only, similar to viewing account statements or trade history. The severity is low because read operations have minimal blast radius—the worst outcome is information disclosure, not asset loss or unwanted transactions.
From the tool's definition Tool retrieves historical records of WBETH unwrap operations including asset conversion details, exchange rates, and transaction status. The verb 'retrieve' and the focus on historical data retrieval indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
The rule that runs BinanceGetWbethUnwrapHistory 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 BinanceGetWbethUnwrapHistory, this is the rule to start with:
BinanceGetWbethUnwrapHistory 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 BinanceGetWbethUnwrapHistory call is checked against it from then on.
Questions about BinanceGetWbethUnwrapHistory
Get WBETH Unwrap History API allows users to retrieve historical records of WBETH unwrap operations, including asset conversion details, exchange rates, and transaction status. 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 BinanceGetWbethUnwrapHistory: 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.
BinanceGetWbethUnwrapHistory 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 BinanceGetWbethUnwrapHistory 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 BinanceGetWbethUnwrapHistory. 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.
BinanceGetWbethUnwrapHistory 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