chrome_network_request · Chrome MCP Server MCP

WHAT IT DOES

What chrome_network_request does on Chrome MCP Server

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

Sending custom HTTP requests is an Execute-category action because it triggers external operations whose effects depend on the arguments (method, URL, payload). It could be used to POST data, call destructive APIs, exfiltrate information, or interact with authenticated services using the browser's existing session/cookies.

From the tool's definition "Send custom HTTP requests" — the tool actively dispatches arbitrary HTTP requests to any URL with presumably any method, headers, and body

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_network_request Rate-limited

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

FAQ

Questions about chrome_network_request

What does the chrome_network_request tool do? +

Send custom HTTP requests. It is categorised as a Execute tool in the Chrome 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 chrome_network_request? +

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

What risk level is chrome_network_request? +

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

Can I rate-limit chrome_network_request? +

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

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

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