Low Risk

browser_get_tabs

Get all open browser tabs with their IDs, URLs, and titles.

How to control browser_get_tabs ↓

AI agents call browser_get_tabs to retrieve information from Cdp Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves metadata about open tabs (IDs, URLs, titles) with no side effects or state modifications. It is a simple information query operation, fitting the Read category. Severity is low because the information exposed is limited to tab metadata already visible to the user, with minimal sensitive data leakage risk in typical usage.

From the tool's definition Tool name 'browser_get_tabs' and description 'Get all open browser tabs with their IDs, URLs, and titles' indicate a retrieval operation that queries existing browser state without modifying or executing actions.

Documented attack patterns abuse exactly the kind of access browser_get_tabs gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Cdp Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_get_tabs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_get_tabs": {}
  }
}

browser_get_tabs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Cdp Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the browser_get_tabs tool do? +

Get all open browser tabs with their IDs, URLs, and titles. It is categorised as a Read tool in the Cdp Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_get_tabs? +

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

What risk level is browser_get_tabs? +

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

Can I rate-limit browser_get_tabs? +

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

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

browser_get_tabs is provided by the Cdp Bridge MCP server (unagi-cq/cdp-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cdp Bridge tool call.

Deterministic rules across all 9 Cdp Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

9 Cdp Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.