chrome_navigate
Navigates Google Chrome to a URL. Pass new_tab=true to open in a new tab.
This record as markdown: /tools/com-local-mcp-local-mcp/chrome-navigate.md
What chrome_navigate does on Local
AI agents invoke chrome_navigate to trigger actions in Local. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
new_tab | boolean | — | |
window_index | integer | — |
Parameters from the server's own tool schema.
Why chrome_navigate is rated High
Navigation of a web browser is an Execute action because it triggers external operations (fetching and rendering content from arbitrary URLs) whose side effects depend entirely on the argument supplied. While not destructive, it can redirect to malicious sites, trigger unwanted downloads, or access sensitive resources.
From the tool's definition Tool 'navigates Google Chrome to a URL' with ability to open new tabs. This executes browser navigation actions whose effects depend on the URL argument provided.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs chrome_navigate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_navigate, this is the rule to start with:
chrome_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every chrome_navigate call is checked against it from then on.
Questions about chrome_navigate
Navigates Google Chrome to a URL. Pass new_tab=true to open in a new tab. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
chrome_navigate accepts 3 parameters: url, new_tab, window_index. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for chrome_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 Local. Nothing to install.
chrome_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 chrome_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 chrome_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.
chrome_navigate is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue