Low Risk

cleanup_all_streams

Close all active WebSocket connections and clean up resources.

How to control cleanup_all_streams ↓

What cleanup_all_streams does on Binance MCP Server

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

Low Risk

Why cleanup_all_streams needs a policy

This tool performs cleanup and resource management of WebSocket connections, which is a housekeeping operation with no side effects on data, financial state, or external systems. It terminates connections that the agent itself initiated, comparable to closing a file handle or disconnecting from a service.

From the tool's definition Tool name 'cleanup_all_streams' and description 'Close all active WebSocket connections and clean up resources' indicate resource management/lifecycle operations. No data retrieval, modification, deletion, code execution, or financial transaction occurs.

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

How to control cleanup_all_streams

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

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

cleanup_all_streams 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 Binance MCP Server — 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.

Related tools and policies

Go deeper

Questions about cleanup_all_streams

What does the cleanup_all_streams tool do? +

Close all active WebSocket connections and clean up resources. 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 cleanup_all_streams? +

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

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

Can I rate-limit cleanup_all_streams? +

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

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

cleanup_all_streams is provided by the Binance MCP Server MCP server (tienan92it/binance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Binance MCP Server tool call.

Start from Binance 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.

29 Binance MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.