chrome_close_tabs · Chrome MCP Server MCP: Risk & Policy

WHAT IT DOES

What chrome_close_tabs does on Chrome MCP Server

AI agents use chrome_close_tabs to create or update resources in Chrome MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome MCP Server environment.

WHY IT NEEDS A POLICY

Why chrome_close_tabs needs a policy

An AI agent can call chrome_close_tabs faster than any human can review — one bad instruction and it creates or modifies resources in Chrome MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_close_tabs Rate-limited

chrome_close_tabs 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "chrome_close_tabs": {
      "limits": [
        {
          "counter": "chrome_close_tabs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome MCP Server, so you can run agents against it safely.

FAQ

Questions about chrome_close_tabs

What does the chrome_close_tabs tool do? +

Close specific tabs or windows. It is categorised as a Write tool in the Chrome MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on chrome_close_tabs? +

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

What risk level is chrome_close_tabs? +

chrome_close_tabs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit chrome_close_tabs? +

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

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

chrome_close_tabs is provided by the Chrome MCP Server MCP server (mnisred/mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.