BinanceGetWbethWrapHistory

Get WBETH Wrap History API allows users to retrieve historical records of WBETH wrap operations, including asset conversion details, exchange rates, and transaction status.

SERVERBinance MCP Server SOURCEnirholas/binance-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-binance-mcp/binancegetwbethwraphistory.md

WHAT IT DOES

What BinanceGetWbethWrapHistory does on Binance MCP Server

AI agents call BinanceGetWbethWrapHistory 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.

RISK

Why BinanceGetWbethWrapHistory is rated Low

This tool only queries and retrieves existing historical data about past wrap operations. It does not create, modify, delete, or execute any transactions. The blast radius of misuse is minimal—an attacker could only access historical transaction information they may not be authorized to see, which is a data confidentiality concern rather than a financial or operational risk. It falls squarely into the Read category.

From the tool's definition Tool retrieves historical records of WBETH wrap operations with 'Get' in the name and description explicitly states 'retrieve historical records' with no modification, deletion, or financial transaction execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs BinanceGetWbethWrapHistory 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 BinanceGetWbethWrapHistory, this is the rule to start with:

BinanceGetWbethWrapHistory Allowed

BinanceGetWbethWrapHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "BinanceGetWbethWrapHistory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceGetWbethWrapHistory call is checked against it from then on.

FAQ

Questions about BinanceGetWbethWrapHistory

What does the BinanceGetWbethWrapHistory tool do? +

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.

How do I enforce a policy on BinanceGetWbethWrapHistory? +

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.

What risk level is BinanceGetWbethWrapHistory? +

BinanceGetWbethWrapHistory is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit BinanceGetWbethWrapHistory? +

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.

How do I block BinanceGetWbethWrapHistory completely? +

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.

What MCP server provides BinanceGetWbethWrapHistory? +

BinanceGetWbethWrapHistory 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.

KEEP EXPLORING

More on Binance MCP Server, and thousands of servers like it.

This server

All 734 Binance MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →