AI agents invoke chrome_navigate to trigger actions in WinScript. 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 in a browser context is an Execute action—it triggers an external application (Chrome) to perform an operation that could load arbitrary content, trigger downloads, execute client-side JavaScript, or interact with web services. While the description is empty, the tool name and sibling context make the function clear.
From the tool's definition Tool name 'chrome_navigate' combined with sibling tools like 'chrome_open', 'chrome_close_tab', 'chrome_find_on_page', 'chrome_get_title', 'chrome_get_url', and 'chrome_new_tab' indicates this is part of a browser automation suite.
Documented attack patterns abuse exactly the kind of access chrome_navigate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WinScript, and nothing reaches the server without passing your rules. This is the rule we recommend for chrome_navigate:
{
"version": "1",
"default": "deny",
"tools": {
"chrome_navigate": {
"limits": [
{
"counter": "chrome_navigate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
chrome_navigate. It is categorised as a Execute tool in the WinScript MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WinScript 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 WinScript. 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 WinScript MCP server (ravaniroshan/winscript-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WinScript, 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.
17 WinScript tools catalogued and risk-classified — across an index of 43,000+ MCP servers.