Low Risk

browser_tabs

browser_tabs

How to control browser_tabs ↓

What browser_tabs does on Playwright

AI agents call browser_tabs as a supporting operation in Playwright workflows.

Low Risk

Why browser_tabs needs a policy

With no description available, the tool likely manages or lists browser tabs based on its name. In the context of a Playwright MCP server with sibling tools like browser_click, browser_close, etc., browser_tabs most likely retrieves or switches between tabs — a Read or minor Write operation. Given the ambiguity, categorizing as Other with low confidence.

From the tool's definition Tool name is 'browser_tabs' but description is empty/uninformative; name alone suggests tab management (listing/switching tabs), which is a Read or low-impact Write operation.

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

How to control browser_tabs

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_tabs": {
      "limits": [
        {
          "counter": "browser_tabs_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_tabs gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Playwright — 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.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_tabs

What does the browser_tabs tool do? +

browser_tabs. It is categorised as a Other tool in the Playwright MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_tabs? +

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

What risk level is browser_tabs? +

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

Can I rate-limit browser_tabs? +

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

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

browser_tabs is provided by the Playwright MCP server (@playwright/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Playwright tool call.

Start from Playwright, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

68 Playwright tools catalogued and risk-classified — across an index of 43,000+ 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.