ws_monitor

Enable or disable WebSocket frame capture.

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-monitor.md

WHAT IT DOES

What ws_monitor does on Jshookmcp

AI agents invoke ws_monitor 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_monitor is rated High

Toggling WebSocket monitoring triggers external interception operations affecting live network traffic.

From the tool's definition Enable or disable WebSocket frame capture

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ws_monitor Rate-limited

ws_monitor 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_monitor": {
      "limits": [
        {
          "counter": "ws_monitor_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_monitor call is checked against it from then on.

FAQ

Questions about ws_monitor

What does the ws_monitor tool do? +

Enable or disable WebSocket frame capture. 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_monitor? +

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

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

Can I rate-limit ws_monitor? +

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

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

ws_monitor 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

monitor_and_analyze_page on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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