List all active WebSocket stream subscriptions.
AI agents call list_active_subscriptions 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.
This tool retrieves information about existing WebSocket subscriptions. It performs no mutation, deletion, execution of commands, or financial operations. The blast radius of misuse is minimal—an agent could at most gain visibility into which market data streams are currently active, which is informational only. Classified as Read with low severity.
From the tool's definition Tool name 'list_active_subscriptions' and description 'List all active WebSocket stream subscriptions' indicate a retrieval/query operation that reads subscription state without modifying data or triggering external actions.
Documented attack patterns abuse exactly the kind of access list_active_subscriptions gives an agent:
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 list_active_subscriptions:
{
"version": "1",
"default": "deny",
"tools": {
"list_active_subscriptions": {}
}
} list_active_subscriptions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active WebSocket stream subscriptions. It is categorised as a Read tool in the Binance MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binance MCP Server MCP server in PolicyLayer and add a rule for list_active_subscriptions: 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.
list_active_subscriptions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_active_subscriptions 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 list_active_subscriptions. 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.
list_active_subscriptions 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.
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.