emulate · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What emulate does on Chrome Devtools

AI agents invoke emulate 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 emulate needs a policy

This tool executes browser-level operations that trigger external effects (emulation changes to a live Chrome instance). It's not merely reading state (Read), nor is it persistently modifying application data (Write), nor is it destructively removing data (Destructive).

From the tool's definition Tool name 'emulate' combined with description 'Emulates various features on the selected page' indicates runtime modification of browser behavior. Context shows this is part of Chrome DevTools which controls a live browser.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

emulate Rate-limited

emulate 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": {
    "emulate": {
      "limits": [
        {
          "counter": "emulate_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 emulate

What does the emulate tool do? +

Emulates various features on the selected page. 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 emulate? +

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

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

Can I rate-limit emulate? +

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

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

emulate is provided by the Chrome Devtools MCP server (zhang77-x/chrpme_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.