chrome_navigate · Chrome MCP Server MCP: Risk & Policy

WHAT IT DOES

What chrome_navigate does on Chrome MCP Server

AI agents invoke chrome_navigate to trigger actions in Chrome MCP Server. 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.

WHY IT NEEDS A POLICY

Why chrome_navigate needs a policy

Navigation to arbitrary URLs is an Execute action: it triggers external operations (page loads, script execution, network requests) whose effects depend on the URL argument. While not destructive or financial, it enables automation of browser behavior that could phish, exfiltrate data via redirect, or inject malicious content.

From the tool's definition Tool name 'chrome_navigate' with description 'Navigate to URLs and control viewport' — navigates to arbitrary URLs and manipulates browser viewport, which triggers network requests, page loads, and can execute third-party scripts and redirect user sessions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_navigate Rate-limited

chrome_navigate 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": {
    "chrome_navigate": {
      "limits": [
        {
          "counter": "chrome_navigate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome MCP Server, so you can run agents against it safely.

FAQ

Questions about chrome_navigate

What does the chrome_navigate tool do? +

Navigate to URLs and control viewport. It is categorised as a Execute tool in the Chrome MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_navigate? +

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

What risk level is chrome_navigate? +

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

Can I rate-limit chrome_navigate? +

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

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

chrome_navigate is provided by the Chrome MCP Server MCP server (mnisred/mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.