browser_hide_highlight · Playwright MCP: Risk & Policy

WHAT IT DOES

What browser_hide_highlight does on Playwright MCP

AI agents invoke browser_hide_highlight to trigger actions in Playwright MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why browser_hide_highlight needs a policy

Based on the tool name, this appears to hide a visual highlight in the browser UI — a minor browser state change. On a browser automation server, this is an Execute-category action (triggers a browser operation), but the blast radius is low as it only affects visual highlighting. Confidence is reduced due to the empty description.

From the tool's definition Tool name 'browser_hide_highlight' on a Playwright browser automation server; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_hide_highlight Rate-limited

browser_hide_highlight stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about browser_hide_highlight

What does the browser_hide_highlight tool do? +

browser_hide_highlight. It is categorised as a Execute tool in the Playwright MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

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 MCP. Nothing to install.

What risk level is browser_hide_highlight? +

browser_hide_highlight is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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 (naumana3services-maker/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.