browser_worker_scripts

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/browser-worker-scripts.md

WHAT IT DOES

What browser_worker_scripts does on Jshookmcp

AI agents call browser_worker_scripts to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browser_worker_scripts is rated Low

Retrieves script data from worker processes without modification; exposure allows source code disclosure.

From the tool's definition dump parsed scripts, get_all_scripts, retrieve worker target information

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_worker_scripts Allowed

browser_worker_scripts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_worker_scripts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about browser_worker_scripts

What does the browser_worker_scripts tool do? +

Attach a CDP session to a worker target and dump its parsed scripts (equivalent to get_all_scripts, but scoped to a worker). Debugger.scriptParsed is replayed on Debugger.enable, so already-loaded worker scripts are returned. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_worker_scripts? +

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

browser_worker_scripts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_worker_scripts? +

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

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

browser_worker_scripts 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →