browser_hide_highlight

A execute tool on the Playwright MCP server.

SERVERPlaywright SOURCEhanato238/playwright-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hanato238-playwright-mcp/browser-hide-highlight.md

What browser_hide_highlight does on Playwright

AI agents invoke browser_hide_highlight to trigger actions in Playwright. 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 browser_hide_highlight is rated High

Based on the tool name, this likely hides a visual highlight/annotation in the browser UI, which is a transient browser state change with minimal blast radius. Classified as Execute since it triggers a browser action, but confidence is low due to empty description. Severity is low as hiding a highlight has negligible impact.

From the tool's definition Tool name 'browser_hide_highlight' suggests a browser UI action; description is empty and uninformative.

Questions about browser_hide_highlight

What does the browser_hide_highlight tool do? +

browser_hide_highlight is a execute tool on the Playwright MCP server. It is categorised as a Execute tool in the Playwright 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. 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 (hanato238/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Playwright, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Playwright's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.