browser_perf_start_coverage · Browser MCP Server MCP

WHAT IT DOES

What browser_perf_start_coverage does on Browser MCP Server

AI agents invoke browser_perf_start_coverage to trigger actions in Browser MCP Server. 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_perf_start_coverage needs a policy

Starting code coverage tracking is an Execute-category action because it triggers an external operation (instrumentation and monitoring of CSS/JavaScript execution) whose effects depend on the browser context and runtime environment. While not destructive or modifying persistent data, it modifies the active browser instrumentation state and captures execution telemetry.

From the tool's definition Tool name 'browser_perf_start_coverage' indicates initiation of code coverage tracking; description states 'Start tracking CSS and JavaScript code coverage'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_perf_start_coverage Rate-limited

browser_perf_start_coverage 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_perf_start_coverage": {
      "limits": [
        {
          "counter": "browser_perf_start_coverage_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 Browser MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_perf_start_coverage

What does the browser_perf_start_coverage tool do? +

Start tracking CSS and JavaScript code coverage (see browser_docs). It is categorised as a Execute tool in the Browser MCP Server 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_perf_start_coverage? +

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

What risk level is browser_perf_start_coverage? +

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

Can I rate-limit browser_perf_start_coverage? +

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

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

browser_perf_start_coverage is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.