websocket_close

Close an open WebSocket session.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Medium RISK CLASS

Category Write

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/websocket-close.md

WHAT IT DOES

What websocket_close does on Jshookmcp

AI agents use websocket_close to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.

RISK

Why websocket_close is rated Medium

An AI agent can call websocket_close faster than any human can review: one bad instruction and it creates or modifies resources in Jshookmcp by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

websocket_close Rate-limited

websocket_close stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "websocket_close": {
      "limits": [
        {
          "counter": "websocket_close_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about websocket_close

What does the websocket_close tool do? +

Close an open WebSocket session. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on websocket_close? +

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

websocket_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit websocket_close? +

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

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

websocket_close 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →