navigate_page
Navigates the currently selected page to a URL.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/navigate-page.md
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 navigate_page is rated High
Navigation to a URL triggers external operations (HTTP requests, JavaScript execution, third-party content loading) whose effects depend entirely on the URL argument. While not destructive or financial in isolation, this is an Execute action because it causes the browser to perform network operations and load potentially untrusted content.
From the tool's definition Tool navigates a browser page to an arbitrary URL specified as an argument. The description states it 'Navigates the currently selected page to a URL' with no restrictions on which URLs are permitted.
Attacks that exploit this kind of access
The rule that runs navigate_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For navigate_page, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome DevTools MCP, apply this rule, and every navigate_page call is checked against it from then on.
Questions about navigate_page
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.
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.
navigate_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
navigate_page is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome DevTools, and thousands of servers like it.
Across the catalogue