graphql_subscribe

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/graphql-subscribe.md

WHAT IT DOES

What graphql_subscribe does on Jshookmcp

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

Establishes live WebSocket connections and executes subscriptions using authenticated browser sessions.

From the tool's definition Open a GraphQL subscription WebSocket, send a subscribe frame, collect frames

Attacks that exploit this kind of access

RECOMMENDED RULE

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

graphql_subscribe Rate-limited

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

FAQ

Questions about graphql_subscribe

What does the graphql_subscribe tool do? +

Open a GraphQL subscription WebSocket, perform the graphql-transport-ws (or legacy graphql-ws) handshake, send a subscribe frame, and collect frames for collectMs. Runs in-page so the browser-session auth (cookies + connectionPayload) is preserved. Pairs with graphql_replay for targets that expose queries/mutations only via the authed WebSocket session. 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 graphql_subscribe? +

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

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

Can I rate-limit graphql_subscribe? +

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

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

graphql_subscribe 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

All high-risk MCP tools → The MCP Attack Database →

Guides

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