list_websocket_connections
Lists tracked WebSocket connections and their frame counts.
This record as markdown: /tools/1600822305-js-reverse-mcp/list-websocket-connections.md
What list_websocket_connections does on Js Reverse
AI agents call list_websocket_connections to retrieve information from Js Reverse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_websocket_connections is rated Low
This tool queries and returns information about WebSocket connections without modifying them, triggering external operations, or causing irreversible changes. It is purely observational for debugging and analysis purposes, consistent with the server's stated goal of supporting JavaScript debugging and API debugging.
From the tool's definition Tool name 'list_websocket_connections' and description 'Lists tracked WebSocket connections and their frame counts' indicate a read-only retrieval of metadata about existing connections.
Attacks that exploit this kind of access
The rule that runs list_websocket_connections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_websocket_connections, this is the rule to start with:
list_websocket_connections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every list_websocket_connections call is checked against it from then on.
Questions about list_websocket_connections
Lists tracked WebSocket connections and their frame counts. It is categorised as a Read tool in the Js Reverse MCP Server, which means it retrieves data without modifying state.
Register the Js Reverse MCP server in PolicyLayer and add a rule for list_websocket_connections: 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 Js Reverse. Nothing to install.
list_websocket_connections 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_websocket_connections 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_websocket_connections. 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_websocket_connections is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
This server
Across the catalogue