# ungroup_tabs

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

Agent View of the PolicyLayer registry record for `ungroup_tabs`. HTML page: https://policylayer.com/tools/2manytabs-mcp-host/ungroup-tabs

## Facts

- Tool: `ungroup_tabs`
- Server: 2manytabs Mcp Host (`2manytabs-mcp-host`) — https://policylayer.com/tools/2manytabs-mcp-host.md
- Install: `npx -y 2manytabs-mcp-host`
- Homepage: https://www.npmjs.com/package/2manytabs-mcp-host
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ungroup_tabs",
    "arguments": {
      "tab_ids": []
    }
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 2manytabs Mcp Host:

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

## Other tools on 2manytabs Mcp Host (9)

- `get_tab_text` — Read — https://policylayer.com/tools/2manytabs-mcp-host/get-tab-text.md
- `list_tab_groups` — Read — https://policylayer.com/tools/2manytabs-mcp-host/list-tab-groups.md
- `list_tabs` — Read — https://policylayer.com/tools/2manytabs-mcp-host/list-tabs.md
- `activate_tab` — Write — https://policylayer.com/tools/2manytabs-mcp-host/activate-tab.md
- `close_tabs` — Write — https://policylayer.com/tools/2manytabs-mcp-host/close-tabs.md
- `group_tabs` — Write — https://policylayer.com/tools/2manytabs-mcp-host/group-tabs.md
- `open_tabs` — Write — https://policylayer.com/tools/2manytabs-mcp-host/open-tabs.md
- `update_tab` — Write — https://policylayer.com/tools/2manytabs-mcp-host/update-tab.md
- `update_tab_group` — Write — https://policylayer.com/tools/2manytabs-mcp-host/update-tab-group.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2manytabs-mcp-host · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2manytabs-mcp-host