navigate_to_url

SERVERChrome Devtools SOURCEbenjaminr/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/benjaminr-chrome-devtools-mcp/navigate-to-url.md

WHAT IT DOES

What navigate_to_url does on Chrome Devtools

AI agents invoke navigate_to_url 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_to_url is rated High

While the tool itself doesn't directly modify or delete data, it executes a browser action that can load arbitrary URLs, potentially triggering malicious websites, phishing pages, or URLs that exploit browser vulnerabilities. This constitutes code/command execution on an external system (Chrome browser).

From the tool's definition "Navigate the connected browser to a specific URL" and "Instructs the currently connected Chrome instance to navigate to the specified URL." This tool directly controls browser navigation, triggering external operations (page loads) whose side effects depend…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

navigate_to_url Rate-limited

navigate_to_url 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_to_url": {
      "limits": [
        {
          "counter": "navigate_to_url_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_to_url call is checked against it from then on.

FAQ

Questions about navigate_to_url

What does the navigate_to_url tool do? +

Navigate the connected browser to a specific URL. Instructs the currently connected Chrome instance to navigate to the specified URL. The function waits briefly for the navigation to begin before returning. Requires an active connection to Chrome established via connect_to_browser or start_chrome with auto_connect. Args: url: Target URL to navigate to. Must be a valid URL that Chrome can load, including HTTP/HTTPS websites, local file paths, or data URIs. Returns: Navigation status dictionary containing: - success: Boolean indicating navigation success - message: Human-readable status description - data: Navigation details including: - url: The URL navigated to - navigated: Boolean navigation status Note: The function returns immediately after initiating navigation and doesn't wait for the page to fully load. Use additional tools to monitor page load completion if needed. 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_to_url? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for navigate_to_url: 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_to_url? +

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

Can I rate-limit navigate_to_url? +

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

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

navigate_to_url is provided by the Chrome Devtools MCP server (benjaminr/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 47 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 →