New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

binance_us_websocket_info

Get information about available WebSocket streams on Binance.US. Returns details about: - Market data streams (public) - User data streams (requires listen key) - Connection URLs and limits

SERVERBinance US MCP Server SOURCEnirholas/binance-us-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-us-mcp/binance-us-websocket-info.md

What binance_us_websocket_info does on Binance US MCP Server

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

Why binance_us_websocket_info is rated Low

This tool retrieves metadata about WebSocket stream availability and configuration. It is informational only—no side effects, no data modification, no financial transactions, and no code execution. Despite the Binance.US context (a financial platform), the specific tool merely provides read-only information about stream endpoints and capabilities.

From the tool's definition Tool description states it 'Get information about available WebSocket streams' and 'Returns details about' connection URLs and stream availability. No mutation, deletion, or execution of trades/transfers occurs.

Questions about binance_us_websocket_info

What does the binance_us_websocket_info tool do? +

Get information about available WebSocket streams on Binance.US. Returns details about: - Market data streams (public) - User data streams (requires listen key) - Connection URLs and limits. It is categorised as a Read tool in the Binance US MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on binance_us_websocket_info? +

Register the Binance US MCP Server MCP server in PolicyLayer and add a rule for binance_us_websocket_info: 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 US MCP Server. Nothing to install.

What risk level is binance_us_websocket_info? +

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

Can I rate-limit binance_us_websocket_info? +

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

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Binance US MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.