Convert dust assets to BNB.
AI agents use BinanceWalletDustTransfer to commit financial operations through Sperax Ecosystem Crypto & DeFI MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool performs an asset conversion/exchange operation, moving cryptocurrency assets (dust) into BNB tokens. This constitutes a financial transaction that changes the composition of a wallet's holdings. Misuse could result in unwanted conversion of assets. The operation is likely irreversible once executed on-chain, and involves financial value movement, making Financial the most appropriate and severe category.
From the tool's definition Convert dust assets to BNB
Documented attack patterns abuse exactly the kind of access BinanceWalletDustTransfer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for BinanceWalletDustTransfer:
{
"version": "1",
"default": "deny",
"tools": {
"BinanceWalletDustTransfer": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to BinanceWalletDustTransfer is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Convert dust assets to BNB. It is categorised as a Financial tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for BinanceWalletDustTransfer: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
BinanceWalletDustTransfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the BinanceWalletDustTransfer 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 BinanceWalletDustTransfer. 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.
BinanceWalletDustTransfer is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.