chrome_setup_check

SERVERLocal SOURCElocal-mcp

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/com-local-mcp-local-mcp/chrome-setup-check.md

WHAT IT DOES

What chrome_setup_check does on Local

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

RISK

Why chrome_setup_check is rated Low

This tool only reads and reports the current configuration state of Google Chrome. It does not modify any data, execute code, or trigger external operations. It is a diagnostic/setup check that returns informational output.

From the tool's definition 'Reports whether Google Chrome is ready' and 'Returns setup instructions if JavaScript from Apple Events is not enabled' — purely a status/diagnostic check with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_setup_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_setup_check, this is the rule to start with:

chrome_setup_check Allowed

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

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

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

FAQ

Questions about chrome_setup_check

What does the chrome_setup_check tool do? +

Reports whether Google Chrome is ready for interactive tools (chrome_click, chrome_type, chrome_evaluate_js, chrome_read_tab text). Returns setup instructions if JavaScript from Apple Events is not enabled. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on chrome_setup_check? +

Register the Local MCP server in PolicyLayer and add a rule for chrome_setup_check: 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 Local. Nothing to install.

What risk level is chrome_setup_check? +

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

Can I rate-limit chrome_setup_check? +

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

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

chrome_setup_check is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

The MCP Attack Database →

Guides

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