navigate_page_history · Chrome DevTools MCP: Risk & Policy

WHAT IT DOES

What navigate_page_history does on Chrome DevTools MCP

AI agents invoke navigate_page_history 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_history needs a policy

Navigation is an Execute action because it triggers external operations (loading web pages, executing page JavaScript, fetching resources) whose side effects depend on the arguments supplied. While seemingly simple, navigation can trigger code execution on the target page and initiate network activity.

From the tool's definition Tool name is 'navigate_page_history' and performs navigation of the currently selected page. The description states it 'Navigates the currently selected page,' which triggers external operations (page loads, network requests) whose effects depend on the URL…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate_page_history Rate-limited

navigate_page_history 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_history": {
      "limits": [
        {
          "counter": "navigate_page_history_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_history

What does the navigate_page_history tool do? +

Navigates the currently selected page. 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_history? +

Register the Chrome DevTools MCP server in PolicyLayer and add a rule for navigate_page_history: 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_history? +

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

Can I rate-limit navigate_page_history? +

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

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

navigate_page_history 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.