navigate_page · Chrome DevTools MCP: Risk & Policy

WHAT IT DOES

What navigate_page does on Chrome DevTools MCP

AI agents invoke navigate_page to trigger actions in Chrome DevTools MCP. 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_page needs a policy

navigate_page triggers browser navigation, which is an external operation with side effects. While navigation itself is not directly destructive or financial, it executes a command whose actual effects (loading potentially malicious sites, triggering unintended transactions, exfiltrating data if the target is attacker-controlled) depend entirely on the URL argument.

From the tool's definition Tool navigates to URLs via Chrome DevTools; URL navigation is an external operation whose effects depend on the argument (the URL). Sibling tools include 'evaluate_script' and 'click' which are clearly Execute-class operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate_page Rate-limited

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

FAQ

Questions about navigate_page

What does the navigate_page tool do? +

Navigates the currently selected page to a URL. It is categorised as a Execute tool in the Chrome DevTools MCP 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_page? +

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

What risk level is navigate_page? +

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

Can I rate-limit navigate_page? +

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

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

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