navigate

Loads a URL

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/navigate.md

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.

RISK

Why navigate is rated High

Navigation is an Execute action because it triggers an external operation (loading a URL in a real browser) whose consequences depend on the argument supplied. While reading content is harmless, an agent could navigate to malicious sites, trigger unwanted downloads, or access sensitive internal URLs.

From the tool's definition Tool 'navigate' "Loads a URL" - this executes a browser navigation action whose effects depend on the provided URL argument. The server description confirms it "control[s] a live Chrome browser" enabling "automated web debugging" and similar operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs navigate safely

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

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.

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

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 (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

browser_navigate on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →