update_tab_group
Update properties of an existing native Chrome Tab Group, including its title, color, or collapsed/expanded state.
This record as markdown: /tools/2manytabs-mcp-host/update-tab-group.md
What update_tab_group does on 2manytabs Mcp Host
AI agents use update_tab_group to create or update resources in 2manytabs Mcp Host, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 2manytabs Mcp Host environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
color | string | — | New color for the group. |
title | string | — | New title for the group. |
group_id | integer | Yes | The numeric ID of the tab group to update (obtained from list_tab_groups or list_tabs). |
collapsed | boolean | — | Whether the group should be collapsed (true) or expanded (false). |
Parameters from the server's own tool schema.
Why update_tab_group is rated Medium
An AI agent can call update_tab_group faster than any human can review: one bad instruction and it creates or modifies resources in 2manytabs Mcp Host by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_tab_group 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 update_tab_group, this is the rule to start with:
update_tab_group stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 2manytabs Mcp Host, apply this rule, and every update_tab_group call is checked against it from then on.
Questions about update_tab_group
Update properties of an existing native Chrome Tab Group, including its title, color, or collapsed/expanded state. It is categorised as a Write tool in the 2manytabs Mcp Host MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_tab_group accepts 4 parameters: color, title, group_id, collapsed. Required: group_id. The full parameter table on this page comes from the server's own tool schema.
Register the 2manytabs Mcp Host MCP server in PolicyLayer and add a rule for update_tab_group: 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.
update_tab_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_tab_group 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 update_tab_group. 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.
update_tab_group 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.
More on 2manytabs Mcp Host, and thousands of servers like it.
This server
Across the catalogue