chrome_list_tabs

Lists every open tab across all Google Chrome windows with title, URL, and whether it is active.

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/chrome-list-tabs.md

WHAT IT DOES

What chrome_list_tabs does on Local

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

RISK

Why chrome_list_tabs is rated Low

This tool performs a read-only query of browser state (tab enumeration) and returns metadata without side effects. It does not create, modify, delete, or execute any operations. The information returned (titles, URLs, active status) is passive observation of existing state.

From the tool's definition Tool name 'chrome_list_tabs' and description 'Lists every open tab across all Google Chrome windows with title, URL, and whether it is active' indicate pure data retrieval with no modification or execution.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_list_tabs safely

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

chrome_list_tabs Allowed

chrome_list_tabs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_list_tabs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every chrome_list_tabs call is checked against it from then on.

FAQ

Questions about chrome_list_tabs

What does the chrome_list_tabs tool do? +

Lists every open tab across all Google Chrome windows with title, URL, and whether it is active. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on chrome_list_tabs? +

Register the Local MCP server in PolicyLayer and add a rule for chrome_list_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 Local. Nothing to install.

What risk level is chrome_list_tabs? +

chrome_list_tabs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit chrome_list_tabs? +

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

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

chrome_list_tabs is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →