Retrieve hashrate statistics for a mining account. It returns both hourly (H_hashrate) and daily (D_hashrate) data, including timestamps, hashrate values, and rejection rates.
AI agents call BinanceAccountList 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 tool retrieves mining account statistics without modifying data, executing code, or creating side effects. It is a read-only query operation. The severity is low because hashrate statistics are non-sensitive operational metrics that do not expose financial transactions, private keys, or account controls.
From the tool's definition Tool name 'BinanceAccountList' and description 'Retrieve hashrate statistics for a mining account' with 'returns' indicate data retrieval with no modification or execution. The return values are passive metrics (hashrate, timestamps, rejection rates).
Documented attack patterns abuse exactly the kind of access BinanceAccountList 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 BinanceAccountList:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceAccountList": {}
}
} BinanceAccountList 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.
Retrieve hashrate statistics for a mining account. It returns both hourly (H_hashrate) and daily (D_hashrate) data, including timestamps, hashrate values, and rejection rates. 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 BinanceAccountList: 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.
BinanceAccountList 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 BinanceAccountList 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 BinanceAccountList. 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.
BinanceAccountList 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.