ws_send_frame

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/ws-send-frame.md

WHAT IT DOES

What ws_send_frame does on Jshookmcp

AI agents invoke ws_send_frame to trigger actions in Jshookmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why ws_send_frame is rated High

Sends arbitrary WebSocket frames to live connections, triggering external operations with unpredictable effects.

From the tool's definition Send a frame through a live in-page WebSocket instance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ws_send_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 ws_send_frame, this is the rule to start with:

ws_send_frame Rate-limited

ws_send_frame stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ws_send_frame": {
      "limits": [
        {
          "counter": "ws_send_frame_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about ws_send_frame

What does the ws_send_frame tool do? +

Send a frame through a live in-page WebSocket instance retained by ws_monitor(exposeInstances=true). Enables edit-and-resend replay of WebSocket traffic. Only reaches WebSockets created AFTER exposeInstances was enabled (existing sockets are not retroactively reachable). It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ws_send_frame? +

Register the Jshook MCP server in PolicyLayer and add a rule for ws_send_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 ws_send_frame? +

ws_send_frame is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ws_send_frame? +

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

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

ws_send_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 → High-risk tools on this server →

Across the catalogue

send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →