websocket_read_frame

Read the next queued WebSocket frame from an open session.

SERVERJshookmcp SOURCE@jshookmcp/jshook

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/io-github-vmoranv-jshookmcp/websocket-read-frame.md

WHAT IT DOES

What websocket_read_frame does on Jshookmcp

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

RISK

Why websocket_read_frame is rated Low

Retrieves queued WebSocket data without modifying state or executing code.

From the tool's definition Read the next queued WebSocket frame from an open session.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs websocket_read_frame safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For websocket_read_frame, this is the rule to start with:

websocket_read_frame Allowed

websocket_read_frame is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "websocket_read_frame": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every websocket_read_frame call is checked against it from then on.

FAQ

Questions about websocket_read_frame

What does the websocket_read_frame tool do? +

Read the next queued WebSocket frame from an open session. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on websocket_read_frame? +

Register the Jshook MCP server in PolicyLayer and add a rule for websocket_read_frame: 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 Jshookmcp. Nothing to install.

What risk level is websocket_read_frame? +

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

Can I rate-limit websocket_read_frame? +

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

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

websocket_read_frame is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

read_input_file on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →