BinanceEarningsList
Retrieves list of earnings related to mining activities, including transferred hashrate, daily hashrate, profit amount, and the status of the payment (unpaid, paying, or paid).
This record as markdown: /tools/nirholas-binance-mcp/binanceearningslist.md
What BinanceEarningsList does on Binance MCP Server
AI agents call BinanceEarningsList 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 BinanceEarningsList is rated Low
This tool performs a read-only operation that queries and displays earnings information without executing any side effects, creating orders, moving funds, or modifying data. The severity is low because reading earnings data poses minimal risk—it merely exposes information the authenticated user already owns, with no capability to transfer funds or execute trades.
From the tool's definition Tool description states it 'Retrieves list of earnings' with no mention of modifications, deletions, or financial transactions. It only queries historical mining earnings data and payment statuses.
Attacks that exploit this kind of access
The rule that runs BinanceEarningsList 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 BinanceEarningsList, this is the rule to start with:
BinanceEarningsList 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 BinanceEarningsList call is checked against it from then on.
Questions about BinanceEarningsList
Retrieves list of earnings related to mining activities, including transferred hashrate, daily hashrate, profit amount, and the status of the payment (unpaid, paying, or paid). 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 BinanceEarningsList: 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.
BinanceEarningsList 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 BinanceEarningsList 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 BinanceEarningsList. 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.
BinanceEarningsList 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