BinanceHashRateResaleList
Returns the list of hashRate resale configurations including transfer details such as algorithm, hashrate amount, sender and receiver pool usernames, start and end dates, and status of the transfer.
This record as markdown: /tools/nirholas-binance-mcp/binancehashrateresalelist.md
What BinanceHashRateResaleList does on Binance MCP Server
AI agents call BinanceHashRateResaleList 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 BinanceHashRateResaleList is rated Low
This tool retrieves existing hashrate resale configuration data from Binance. It queries and returns information about transfer details, algorithms, amounts, usernames, dates, and status. There is no indication of creating, modifying, deleting, or executing operations. The impact is limited to read-only access to configuration metadata, making it a Read category tool with low severity.
From the tool's definition Tool 'Returns the list of hashRate resale configurations' — uses 'Returns' and 'list', indicating data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs BinanceHashRateResaleList 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 BinanceHashRateResaleList, this is the rule to start with:
BinanceHashRateResaleList 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 BinanceHashRateResaleList call is checked against it from then on.
Questions about BinanceHashRateResaleList
Returns the list of hashRate resale configurations including transfer details such as algorithm, hashrate amount, sender and receiver pool usernames, start and end dates, and status of the transfer. 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 BinanceHashRateResaleList: 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.
BinanceHashRateResaleList 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 BinanceHashRateResaleList 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 BinanceHashRateResaleList. 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.
BinanceHashRateResaleList 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