browser_jsdom_cookies

Manage cookies on a JSDOM session. Isolated from the attached browser.

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/browser-jsdom-cookies.md

WHAT IT DOES

What browser_jsdom_cookies does on Jshookmcp

AI agents use browser_jsdom_cookies 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 browser_jsdom_cookies is rated Medium

Tool creates or modifies cookie data, reversible action with moderate blast radius if misused.

From the tool's definition Manage cookies on a JSDOM session

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_jsdom_cookies Rate-limited

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

FAQ

Questions about browser_jsdom_cookies

What does the browser_jsdom_cookies tool do? +

Manage cookies on a JSDOM session. Isolated from the attached browser. 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 browser_jsdom_cookies? +

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

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

Can I rate-limit browser_jsdom_cookies? +

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

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

browser_jsdom_cookies 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 →