BinanceGetSolRedemptionHistory

Get SOL Redemption History API allows users to retrieve their SOL redemption history, detailing the amount of BNSOL redeemed for SOL and the exchange rate.

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/binancegetsolredemptionhistory.md

WHAT IT DOES

What BinanceGetSolRedemptionHistory does on Binance MCP Server

AI agents call BinanceGetSolRedemptionHistory 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 BinanceGetSolRedemptionHistory is rated Low

This tool retrieves historical redemption data (amount of BNSOL redeemed for SOL and exchange rate) with no side effects. It is a pure read operation that does not create, modify, delete, or execute any transactions. While it relates to financial operations (staking/redemption), the tool itself only queries past data rather than moving money or committing new obligations.

From the tool's definition The tool description states it 'allows users to retrieve their SOL redemption history' — a read-only operation that queries historical transaction data without modifying or executing any actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

BinanceGetSolRedemptionHistory Allowed

BinanceGetSolRedemptionHistory 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": {
    "BinanceGetSolRedemptionHistory": {}
  }
}

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 BinanceGetSolRedemptionHistory call is checked against it from then on.

FAQ

Questions about BinanceGetSolRedemptionHistory

What does the BinanceGetSolRedemptionHistory tool do? +

Get SOL Redemption History API allows users to retrieve their SOL redemption history, detailing the amount of BNSOL redeemed for SOL and the exchange rate. 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 BinanceGetSolRedemptionHistory? +

Register the Binance MCP Server MCP server in PolicyLayer and add a rule for BinanceGetSolRedemptionHistory: 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 BinanceGetSolRedemptionHistory? +

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

Can I rate-limit BinanceGetSolRedemptionHistory? +

Yes. Add a rate_limit block to the BinanceGetSolRedemptionHistory 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 BinanceGetSolRedemptionHistory completely? +

Set action: deny in the PolicyLayer policy for BinanceGetSolRedemptionHistory. 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 BinanceGetSolRedemptionHistory? +

BinanceGetSolRedemptionHistory 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 →