# list_tab_groups

List all existing native Chrome Tab Groups in the current browser session. Returns their IDs, titles, colors, collapsed states, and parent window IDs.

Agent View of the PolicyLayer registry record for `list_tab_groups`. HTML page: https://policylayer.com/tools/2manytabs-mcp-host/list-tab-groups

## Facts

- Tool: `list_tab_groups`
- 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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `title_query` | string | no | Case-insensitive substring filter for group titles. |

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": "list_tab_groups",
    "arguments": {}
  }
}
```

## Why list_tab_groups is rated Low

Even though list_tab_groups only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call list_tab_groups to retrieve information from 2manytabs Mcp Host without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tab_groups": {}
  }
}
```

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

- `ungroup_tabs` — Destructive — https://policylayer.com/tools/2manytabs-mcp-host/ungroup-tabs.md
- `get_tab_text` — Read — https://policylayer.com/tools/2manytabs-mcp-host/get-tab-text.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