start_css_coverage_tracking

Start tracking CSS rule usage for coverage analysis. Returns: Status of coverage tracking initialization

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-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/benjaminr-chrome-devtools-mcp/start-css-coverage-tracking.md

WHAT IT DOES

What start_css_coverage_tracking does on Chrome Devtools

AI agents invoke start_css_coverage_tracking 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.

RISK

Why start_css_coverage_tracking is rated High

This tool executes an operation that initiates a browser-side process (CSS coverage analysis). While it doesn't directly execute arbitrary code or delete data, it modifies browser behavior by activating DevTools instrumentation. The broader context of sibling tools like 'execute_javascript', 'evaluate_in_all_frames', and 'connect_to_browser' confirms this is an Execute category server.

From the tool's definition Tool initiates CSS coverage tracking via Chrome DevTools Protocol, which monitors and collects runtime data about CSS usage.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_css_coverage_tracking safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_css_coverage_tracking, this is the rule to start with:

start_css_coverage_tracking Rate-limited

start_css_coverage_tracking 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": {
    "start_css_coverage_tracking": {
      "limits": [
        {
          "counter": "start_css_coverage_tracking_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every start_css_coverage_tracking call is checked against it from then on.

FAQ

Questions about start_css_coverage_tracking

What does the start_css_coverage_tracking tool do? +

Start tracking CSS rule usage for coverage analysis. Returns: Status of coverage tracking initialization. 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 start_css_coverage_tracking? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for start_css_coverage_tracking: 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 start_css_coverage_tracking? +

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

Can I rate-limit start_css_coverage_tracking? +

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

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

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

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 47 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →