BinanceMiningAccountEarning
Retrieves the earnings associated with a mining account, including the type of earnings (e.g., rebate, referral, refund), sub-account ID, the mining account name, and the amount earned. It also supports pagination for large data sets.
This record as markdown: /tools/nirholas-binance-mcp/binanceminingaccountearning.md
What BinanceMiningAccountEarning does on Binance MCP Server
AI agents call BinanceMiningAccountEarning 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.
Why BinanceMiningAccountEarning is rated Low
This tool performs a read-only query of historical mining earnings data. It retrieves existing data without modifying, deleting, executing code, or moving funds. The blast radius of misuse is minimal—an attacker could view earnings information they may not be authorized to see, but cannot alter balances, execute trades, or cause financial harm. Classification as Read with low severity is appropriate.
From the tool's definition Tool description explicitly states it 'Retrieves the earnings associated with a mining account' with support for 'pagination for large data sets'.
Attacks that exploit this kind of access
The rule that runs BinanceMiningAccountEarning 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 BinanceMiningAccountEarning, this is the rule to start with:
BinanceMiningAccountEarning is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceMiningAccountEarning call is checked against it from then on.
Questions about BinanceMiningAccountEarning
Retrieves the earnings associated with a mining account, including the type of earnings (e.g., rebate, referral, refund), sub-account ID, the mining account name, and the amount earned. It also supports pagination for large data sets. 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 BinanceMiningAccountEarning: 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.
BinanceMiningAccountEarning 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 BinanceMiningAccountEarning 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 BinanceMiningAccountEarning. 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.
BinanceMiningAccountEarning 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.
More on Binance MCP Server, and thousands of servers like it.
This server
Across the catalogue