AI agents call chrome_close_tab to permanently remove resources in WinScript — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing a browser tab is typically irreversible in an automated context — the tab's session state, unsaved form data, and navigation history are lost. Given sibling tools like chrome_open and chrome_new_tab, this tool likely closes an active tab, which cannot be undone programmatically. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'chrome_close_tab'; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access chrome_close_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_close_tab:
{
"version": "1",
"default": "deny",
"hide": [
"chrome_close_tab"
]
}chrome_close_tab disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
chrome_close_tab. It is categorised as a Destructive tool in the WinScript MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the WinScript MCP server in PolicyLayer and add a rule for chrome_close_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_close_tab is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the chrome_close_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_close_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_close_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.