clear_highlight_and_stop_recording · Chrome Devtools MCP

WHAT IT DOES

What clear_highlight_and_stop_recording does on Chrome Devtools

AI agents invoke clear_highlight_and_stop_recording to trigger actions in Chrome Devtools. 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 clear_highlight_and_stop_recording needs a policy

This tool performs browser control actions — clearing a highlight and stopping/finalizing a recording session. These are external operations with side effects on the live browser's state. Stopping and finalizing a recording may produce or commit recorded data.

From the tool's definition 'stop and finalize the active recording' and 'clear active highlight' indicate triggering browser state changes and finalizing an ongoing recording operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clear_highlight_and_stop_recording Rate-limited

clear_highlight_and_stop_recording 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": {
    "clear_highlight_and_stop_recording": {
      "limits": [
        {
          "counter": "clear_highlight_and_stop_recording_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 Chrome Devtools, so you can run agents against it safely.

FAQ

Questions about clear_highlight_and_stop_recording

What does the clear_highlight_and_stop_recording tool do? +

Best-effort clear active highlight, then stop and finalize the active recording. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on clear_highlight_and_stop_recording? +

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

What risk level is clear_highlight_and_stop_recording? +

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

Can I rate-limit clear_highlight_and_stop_recording? +

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

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

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