BinanceWalletDustlog

Get dust log (history of dust transfers).

SERVERBinance MCP Server SOURCEnirholas/binance-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-binance-mcp/binancewalletdustlog.md

WHAT IT DOES

What BinanceWalletDustlog does on Binance MCP Server

AI agents call BinanceWalletDustlog 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.

RISK

Why BinanceWalletDustlog is rated Low

This tool retrieves historical records of dust transfers from a wallet, which is a Read operation. Dust in crypto contexts refers to small amounts of cryptocurrency left over from trading. Accessing this log has no side effects, does not modify any data, and poses minimal security risk even if misused by an agent—it only exposes historical transaction metadata that the account owner would already have access to.

From the tool's definition Tool name indicates 'Get dust log (history of dust transfers)' — a read-only retrieval of past transaction history with no modification, creation, or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs BinanceWalletDustlog 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 BinanceWalletDustlog, this is the rule to start with:

BinanceWalletDustlog Allowed

BinanceWalletDustlog is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "BinanceWalletDustlog": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Binance MCP Server, apply this rule, and every BinanceWalletDustlog call is checked against it from then on.

FAQ

Questions about BinanceWalletDustlog

What does the BinanceWalletDustlog tool do? +

Get dust log (history of dust transfers). It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on BinanceWalletDustlog? +

Register the Binance MCP Server MCP server in PolicyLayer and add a rule for BinanceWalletDustlog: 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.

What risk level is BinanceWalletDustlog? +

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

Can I rate-limit BinanceWalletDustlog? +

Yes. Add a rate_limit block to the BinanceWalletDustlog 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 BinanceWalletDustlog completely? +

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

BinanceWalletDustlog 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.

KEEP EXPLORING

More on Binance MCP Server, and thousands of servers like it.

This server

All 734 Binance MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →