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.
AI agents call BinanceGetSolRedemptionHistory 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 is a straightforward data retrieval operation. While it accesses financial history within a Binance account, it has no side effects and cannot execute trades, modify balances, or commit new financial obligations. The worst misuse would be information disclosure of redemption history, which poses minimal risk compared to tools that can execute trades or move funds.
From the tool's definition Tool retrieves historical redemption data ('Get SOL Redemption History API allows users to retrieve their SOL redemption history'). No modification, deletion, or financial transaction is performed—it only queries past redemption records.
Documented attack patterns abuse exactly the kind of access BinanceGetSolRedemptionHistory 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 BinanceGetSolRedemptionHistory:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceGetSolRedemptionHistory": {}
}
}BinanceGetSolRedemptionHistory 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 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.
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.
BinanceGetSolRedemptionHistory 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 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.
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.
BinanceGetSolRedemptionHistory 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.