Low Risk

browser_hide_highlight

browser_hide_highlight

How to control browser_hide_highlight ↓

What browser_hide_highlight does on Playwright

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

Low Risk

Why browser_hide_highlight needs a policy

Based on the name, this tool likely hides or removes a visual highlight overlay in the browser viewport. This is a cosmetic/UI operation with no data modification, execution, or destructive effects. The empty description lowers confidence significantly. Given sibling tool 'browser_annotate', this likely undoes a visual annotation display — a low-risk read/UI state change that fits 'Other' best.

From the tool's definition Tool name 'browser_hide_highlight' with empty description. Name suggests hiding a visual highlight/annotation in the browser.

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

How to control browser_hide_highlight

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_hide_highlight:

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

browser_hide_highlight 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_hide_highlight

What does the browser_hide_highlight tool do? +

browser_hide_highlight. 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_hide_highlight? +

Register the Playwright MCP server in PolicyLayer and add a rule for browser_hide_highlight: 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_hide_highlight? +

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

Can I rate-limit browser_hide_highlight? +

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

Set action: deny in the PolicyLayer policy for browser_hide_highlight. 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_hide_highlight? +

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