emulate_network · Chrome DevTools MCP: Risk & Policy

WHAT IT DOES

What emulate_network does on Chrome DevTools MCP

AI agents invoke emulate_network to trigger actions in Chrome DevTools MCP. 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_network needs a policy

This tool executes an operation that changes the execution environment of a web page (network throttling, offline simulation). While it doesn't modify persistent data or run arbitrary code, it triggers external operations whose effects depend on the arguments provided (which throttling profile, whether offline, etc.).

From the tool's definition Tool 'emulates network conditions such as throttling or offline mode' - this actively modifies runtime browser behavior through Chrome DevTools protocol, affecting how the page operates.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

emulate_network Rate-limited

emulate_network 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_network": {
      "limits": [
        {
          "counter": "emulate_network_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 MCP, so you can run agents against it safely.

FAQ

Questions about emulate_network

What does the emulate_network tool do? +

Emulates network conditions such as throttling or offline mode on the selected page. It is categorised as a Execute tool in the Chrome DevTools MCP 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_network? +

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

What risk level is emulate_network? +

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

Can I rate-limit emulate_network? +

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

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

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