browser_list_workers

Enumerate Service Worker / Shared Worker / dedicated Web Worker targets via Target.getTargets. Use browser_worker_scripts(targetId=...) afterwards to dump a worker

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-list-workers.md

WHAT IT DOES

What browser_list_workers does on Jshookmcp

AI agents call browser_list_workers 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_list_workers is rated Low

Tool lists worker targets and retrieves scripts; no modification, deletion, or execution of code.

From the tool's definition Enumerate Service Worker targets via Target.getTargets; dump worker scripts.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_list_workers Allowed

browser_list_workers 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_list_workers": {}
  }
}

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_list_workers call is checked against it from then on.

FAQ

Questions about browser_list_workers

What does the browser_list_workers tool do? +

Enumerate Service Worker / Shared Worker / dedicated Web Worker targets via Target.getTargets. Use browser_worker_scripts(targetId=...) afterwards to dump a worker. 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_list_workers? +

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

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

Can I rate-limit browser_list_workers? +

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

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

browser_list_workers 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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