Low Risk

BinanceRequestForMinerList

Retrieves a list of miners (workers) associated with a mining account, including details such as miner name, status, real-time hashrate, 24H hashrate, rejection rate, and last submission time.

How to control BinanceRequestForMinerList ↓

AI agents call BinanceRequestForMinerList to retrieve information from BNB Chain MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries mining account information and returns miner details without side effects. It is purely informational and does not modify, execute, or delete any data. The blast radius of misuse is minimal — an attacker could gain visibility into mining operations but cannot perform transactions, execute code, or alter system state.

From the tool's definition Tool retrieves a list of miners with details (name, status, hashrate, rejection rate, last submission time) — no modification, deletion, or execution of operations.

Documented attack patterns abuse exactly the kind of access BinanceRequestForMinerList gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and BNB Chain MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceRequestForMinerList:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "BinanceRequestForMinerList": {}
  }
}

BinanceRequestForMinerList is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register BNB Chain MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the BinanceRequestForMinerList tool do? +

Retrieves a list of miners (workers) associated with a mining account, including details such as miner name, status, real-time hashrate, 24H hashrate, rejection rate, and last submission time. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on BinanceRequestForMinerList? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for BinanceRequestForMinerList: 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 BNB Chain MCP. Nothing to install.

What risk level is BinanceRequestForMinerList? +

BinanceRequestForMinerList is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit BinanceRequestForMinerList? +

Yes. Add a rate_limit block to the BinanceRequestForMinerList 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.

How do I block BinanceRequestForMinerList completely? +

Set action: deny in the PolicyLayer policy for BinanceRequestForMinerList. 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.

What MCP server provides BinanceRequestForMinerList? +

BinanceRequestForMinerList is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.