AI agents invoke chrome_new_tab 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.
Opening a new tab is an Execute action because it initiates a browser operation whose side effects depend on context and subsequent navigation. While not destructive or financial, it performs an action in an external application rather than merely reading data. The empty description lowers confidence slightly, but the tool name and server context are clear.
From the tool's definition Tool name 'chrome_new_tab' combined with server's stated capability of 'UI interaction' and 'app control' via browser automation (evidenced by sibling tools like chrome_open, chrome_navigate, chrome_close_tab).
Documented attack patterns abuse exactly the kind of access chrome_new_tab 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_new_tab:
{
"version": "1",
"default": "deny",
"tools": {
"chrome_new_tab": {
"limits": [
{
"counter": "chrome_new_tab_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}chrome_new_tab 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_new_tab. 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_new_tab: 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_new_tab 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_new_tab 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_new_tab. 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_new_tab 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.