chrome_launch · Nextjs Agent MCP: Risk & Policy

WHAT IT DOES

What chrome_launch does on Nextjs Agent

AI agents invoke chrome_launch to trigger actions in Nextjs Agent. 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_launch needs a policy

Launching Chrome with remote debugging enables arbitrary code execution in a browser context. While not immediately destructive, it can execute scripts, interact with web pages, and potentially access sensitive data depending on the profile and permissions.

From the tool's definition Tool name and description indicate 'Launch Chrome with remote debugging' — this executes a browser process with debugging capabilities, which can interact with web content, run scripts, and trigger external operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome_launch Rate-limited

chrome_launch 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_launch": {
      "limits": [
        {
          "counter": "chrome_launch_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 Nextjs Agent, so you can run agents against it safely.

FAQ

Questions about chrome_launch

What does the chrome_launch tool do? +

Launch Chrome with remote debugging and a chosen profile directory (. It is categorised as a Execute tool in the Nextjs Agent 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_launch? +

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

What risk level is chrome_launch? +

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

Can I rate-limit chrome_launch? +

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

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

chrome_launch is provided by the Nextjs Agent MCP server (zohaib3249/nextjs-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

chrome_launch is one line of Nextjs Agent's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →