New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

chrome_navigate_to_url

Navigate the current browser tab to a specific URL

SERVERChrome Feedback SOURCE2019-02-18/mcx
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about chrome_navigate_to_url

What does the chrome_navigate_to_url tool do? +

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.

How do I enforce a policy on chrome_navigate_to_url? +

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.

What risk level is chrome_navigate_to_url? +

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

Can I rate-limit chrome_navigate_to_url? +

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.

How do I block chrome_navigate_to_url completely? +

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.

What MCP server provides chrome_navigate_to_url? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Chrome Feedback's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.