// SCAN REPORT

Node2flow/binance

23 tools. 6 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 2 Jul 2026

6 can modify or destroy data

17 read-only

23 tools total

Community server · catalogue entry verified 02/07/2026

How to control Node2flow/binance ↓

TOOL MAP

What Node2flow/binance exposes to your agents

Read (17) Write / Execute (3) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Node2flow/binance tools

Financial · Critical bn_new_order This tool directly places live trading orders on Binance using real funds. Destructive · Critical bn_cancel_all_orders This tool cancels all pending orders for a trading symbol, which is an irreversible operation that destroys/removes active financial orders. Destructive · High bn_cancel_order Cancelling an order is an irreversible action — once cancelled, the order cannot be reinstated. Execute · Medium bn_close_listen_key This tool terminates an active user data stream by invalidating a listen key.

6 of Node2flow/binance's 23 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Node2flow/binance

PolicyLayer is an MCP gateway — it sits between your AI agents and Node2flow/binance, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "bn_new_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "bn_cancel_all_orders": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "bn_keepalive_listen_key": {
    "limits": [
      {
        "counter": "bn_keepalive_listen_key_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "bn_account_info": {
    "limits": [
      {
        "counter": "bn_account_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Node2flow/binance — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NODE2FLOW/BINANCE →

Instant setup, no code required.

FULL CATALOGUE

All 23 Node2flow/binance tools

FINANCIAL 1 tools

Financial bn_new_order Place a new order. WARNING: This uses REAL MONEY on Binance Global. Supports LIMIT, MARKET, STOP_LOSS, STOP_LO

DESTRUCTIVE 2 tools

Destructive bn_cancel_all_orders Cancel all open orders for a symbol. WARNING: This cancels ALL pending orders at once. Cannot be undone. Destructive bn_cancel_order Cancel an active order by orderId or origClientOrderId.

EXECUTE 2 tools

Execute bn_close_listen_key Close/invalidate a listen key. The associated user data stream will be terminated. Execute bn_create_listen_key Create a listen key for user data stream (WebSocket). The key is valid for 60 minutes. Use keepalive to extend

WRITE 1 tools

Write bn_keepalive_listen_key Keepalive a listen key to extend its validity by 60 minutes. Should be called periodically to prevent expirati

READ 17 tools

Read bn_account_info Get account information including balances, commission rates, and trading permissions. Returns all asset balan Read bn_aggregate_trades Get compressed/aggregate trades for a symbol. Trades that fill at the same time, price, and side are aggregate Read bn_all_orders Get all orders (active, canceled, filled) for a symbol. Supports time range and pagination via orderId. Read bn_avg_price Get current average price for a symbol. Returns the weighted average price over the last 5 minutes. Read bn_book_ticker Get best bid/ask price and quantity for a symbol or all symbols. Useful for spread analysis. Read bn_exchange_info Get exchange information including trading rules, symbol list, filters (PRICE_FILTER, LOT_SIZE, MIN_NOTIONAL), Read bn_klines Get candlestick/kline data (OHLCV) for a symbol. Returns arrays of [openTime, open, high, low, close, volume, Read bn_my_trades Get trade execution history for a specific symbol. Returns price, quantity, commission, and whether you were b Read bn_open_orders Get all open orders for a symbol or all symbols. Weight: 3 (with symbol), 40 (without symbol). Read bn_order_book Get order book (bids and asks) for a symbol. Weight varies by limit: 5 (1-100), 25 (101-500), 50 (501-1000), 2 Read bn_ping Test connectivity to Binance API. Returns empty object if successful. Use to verify API is reachable. Read bn_query_order Query a specific order by orderId or origClientOrderId. Returns order status, filled quantity, and execution d Read bn_recent_trades Get recent trades for a symbol. Returns up to 1000 most recent trades with price, quantity, and time. Read bn_server_time Get Binance server time (millisecond timestamp). Use to check connectivity and sync timestamps for signed requ Read bn_test_order Test new order creation (dry run). Validates all parameters without actually placing the order. No funds are u Read bn_ticker_24hr Get 24-hour price change statistics. Weight: 2 (single symbol), 80 (all symbols). Includes price change, volum Read bn_ticker_price Get latest price for a symbol or all symbols. Lightweight endpoint for quick price checks.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Node2flow/binance

Can an AI agent move money through the Node2flow/binance MCP server? +

Yes. The Node2flow/binance server exposes 1 financial tools including bn_new_order. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Node2flow/binance MCP server? +

Yes. The Node2flow/binance server exposes 2 destructive tools including bn_cancel_all_orders, bn_cancel_order. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Node2flow/binance? +

The Node2flow/binance server has 1 write tools including bn_keepalive_listen_key. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Node2flow/binance.

How many tools does the Node2flow/binance MCP server expose? +

23 tools across 4 categories: Destructive, Execute, Read, Write. 17 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Node2flow/binance? +

Register the Node2flow/binance MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Node2flow/binance tool call.

Deterministic rules across all 23 Node2flow/binance tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NODE2FLOW/BINANCE →

Instant setup, no code required.

23 Node2flow/binance tools catalogued and risk-classified — across an index of 43,000+ MCP servers.