ungroup_tabs

Remove one or more open Chrome tabs from their current native Tab Groups.

SERVER2manytabs Mcp Host SOURCE2manytabs-mcp-host

Critical RISK CLASS

Category Destructive

Parameters 11 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/2manytabs-mcp-host/ungroup-tabs.md

WHAT IT DOES

What ungroup_tabs does on 2manytabs Mcp Host

AI agents call ungroup_tabs to permanently remove resources in 2manytabs Mcp Host, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`tab_ids`	array	Yes	Array of tab IDs to remove from any groups.

Parameters from the server's own tool schema.

RISK

Why ungroup_tabs is rated Critical

An AI agent that decides to call ungroup_tabs doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 2manytabs Mcp Host is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ungroup_tabs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 2manytabs Mcp Host, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ungroup_tabs, this is the rule to start with:

ungroup_tabs Hidden

ungroup_tabs is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "ungroup_tabs"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 2manytabs Mcp Host, apply this rule, and every ungroup_tabs call is checked against it from then on.

FAQ

Questions about ungroup_tabs

What does the ungroup_tabs tool do? +

Remove one or more open Chrome tabs from their current native Tab Groups. It is categorised as a Destructive tool in the 2manytabs Mcp Host MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does ungroup_tabs accept? +

ungroup_tabs accepts 1 parameter: tab_ids. Required: tab_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ungroup_tabs? +

Register the 2manytabs Mcp Host MCP server in PolicyLayer and add a rule for ungroup_tabs: 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 2manytabs Mcp Host. Nothing to install.

What risk level is ungroup_tabs? +

ungroup_tabs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit ungroup_tabs? +

Yes. Add a rate_limit block to the ungroup_tabs 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 ungroup_tabs completely? +

Set action: deny in the PolicyLayer policy for ungroup_tabs. 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 ungroup_tabs? +

ungroup_tabs is provided by the 2manytabs Mcp Host MCP server (2manytabs-mcp-host). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 2manytabs Mcp Host, and thousands of servers like it.

This server

All 10 2manytabs Mcp Host tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →