Get WBETH Wrap History API allows users to retrieve historical records of WBETH wrap operations, including asset conversion details, exchange rates, and transaction status.
AI agents call BinanceGetWbethWrapHistory to retrieve information from Binance MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves past transaction history and does not create, modify, delete, or execute any state-changing operations. While it is part of a financial exchange platform, it only reads existing historical data rather than executing trades, moving funds, or committing financial obligations. The blast radius of misuse is minimal as it only exposes past transaction information.
From the tool's definition Tool description states it 'allows users to retrieve historical records' of WBETH wrap operations, including 'conversion details, exchange rates, and transaction status.' The verb 'retrieve' and focus on historical records indicates a read-only operation with…
Documented attack patterns abuse exactly the kind of access BinanceGetWbethWrapHistory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binance MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceGetWbethWrapHistory:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceGetWbethWrapHistory": {}
}
}BinanceGetWbethWrapHistory 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 WBETH Wrap History API allows users to retrieve historical records of WBETH wrap 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 BinanceGetWbethWrapHistory: 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.
BinanceGetWbethWrapHistory 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 BinanceGetWbethWrapHistory 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 BinanceGetWbethWrapHistory. 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.
BinanceGetWbethWrapHistory is provided by the Binance MCP Server MCP server (termix-official/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 160 Binance MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
160 Binance MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.