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.
Navigation is not a passive read operation—it triggers active browser behavior and side effects determined by the supplied URL. An AI agent with this tool could be tricked into navigating to malicious sites, phishing pages, or URLs designed to exfiltrate data.
From the tool's definition Tool name 'navigate' with description 'Loads a URL'. In the context of Chrome DevTools control, this initiates browser navigation which is an external operation whose effects depend on the URL argument (could redirect to phishing, malware, or exfiltration…
Documented attack patterns abuse exactly the kind of access navigate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome DevTools, and nothing reaches the server without passing your rules. This is the rule we recommend for navigate:
{
"version": "1",
"default": "deny",
"tools": {
"navigate": {
"limits": [
{
"counter": "navigate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
navigate 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 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. 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 is provided by the Chrome DevTools MCP server (ChromeDevTools/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome DevTools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
50 Chrome DevTools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.