navigate · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What navigate does on Chrome Devtools

AI agents invoke navigate to trigger actions in Chrome Devtools. 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 navigate needs a policy

Navigate is not merely Read (it doesn't just query data—it causes the browser to fetch and load a resource). It's not Write (navigation doesn't create/modify persistent data under the agent's control). It's Execute because loading a URL initiates network activity and may trigger arbitrary code execution on the loaded page.

From the tool's definition Tool is named 'navigate' and described as 'Loads a URL'. In the context of browser automation via DevTools, URL navigation is an Execute action because it triggers external operations (network requests, page loads, script execution) whose effects depend on…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate Rate-limited

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": {
    "navigate": {
      "limits": [
        {
          "counter": "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 Devtools, so you can run agents against it safely.

FAQ

Questions about navigate

What does the navigate tool do? +

Loads a URL. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate? +

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

What risk level is navigate? +

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

Can I rate-limit navigate? +

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

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

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