Get SOL Staking History API allows users to retrieve their SOL staking history, including details about the amount of SOL staked, the equivalent BNSOL amount distributed, the exchange rate, and the status of each staking.
AI agents call BinanceGetSolStakingHistory to retrieve information from Sperax Ecosystem Crypto & DeFI 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 read-only query tool that retrieves historical staking data. It has no side effects, does not execute code or transactions, does not create or modify data, and does not move funds. The blast radius of misuse is minimal—an attacker could view sensitive staking history but cannot perform harmful actions through this tool alone.
From the tool's definition Tool name 'BinanceGetSolStakingHistory' and description state it 'allows users to retrieve their SOL staking history' with details about 'amount of SOL staked' and 'exchange rate' — purely informational retrieval with no modification, deletion, or execution…
Documented attack patterns abuse exactly the kind of access BinanceGetSolStakingHistory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceGetSolStakingHistory:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceGetSolStakingHistory": {}
}
}BinanceGetSolStakingHistory 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 Staking History API allows users to retrieve their SOL staking history, including details about the amount of SOL staked, the equivalent BNSOL amount distributed, the exchange rate, and the status of each staking. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for BinanceGetSolStakingHistory: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
BinanceGetSolStakingHistory 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 BinanceGetSolStakingHistory 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 BinanceGetSolStakingHistory. 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.
BinanceGetSolStakingHistory is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.