chrome_navigate_to_url
Navigate the current browser tab to a specific URL
This record as markdown: /tools/2019-02-18-mcx/chrome-navigate-to-url.md
What chrome_navigate_to_url does on Chrome Feedback
AI agents invoke chrome_navigate_to_url to trigger actions in Chrome Feedback. 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 chrome_navigate_to_url is rated High
Navigation is an external operation that triggers side effects (loading pages, executing scripts on those pages, potential for phishing or malicious site access). While not destructive or financial, it qualifies as Execute because it runs a browser action whose consequences depend on arguments.
From the tool's definition Tool performs 'Navigate the current browser tab to a specific URL' — a direct action that changes browser state and loads external content. This is a browser automation action whose effects depend on the URL argument provided.
Attacks that exploit this kind of access
The rule that runs chrome_navigate_to_url safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Feedback, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_navigate_to_url, this is the rule to start with:
chrome_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Feedback, apply this rule, and every chrome_navigate_to_url call is checked against it from then on.
Questions about chrome_navigate_to_url
Navigate the current browser tab to a specific URL. It is categorised as a Execute tool in the Chrome Feedback MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_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 Feedback. Nothing to install.
chrome_navigate_to_url 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 chrome_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.
Set action: deny in the PolicyLayer policy for chrome_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.
chrome_navigate_to_url is provided by the Chrome Feedback MCP server (2019-02-18/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Feedback, and thousands of servers like it.
Across the catalogue