// SCAN REPORT

DevServer MCP

11 tools. 6 can modify or destroy data without limits.

6 write tools that can modify data. Rate limits recommended.

Last updated: 1 Jul 2026

6 can modify or destroy data

5 read-only

11 tools total

Community server · catalogue entry verified 01/07/2026

How to control DevServer MCP ↓

TOOL MAP

What DevServer MCP exposes to your agents

Read (5) Write / Execute (6) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous DevServer MCP tools

Execute · High browser_navigate Browser navigation is an Execute action: it programmatically controls a browser to visit URLs or navigate between pages, causing side effects that depend on the target argument (which URL to navigate to, what content loa Execute · High start_server Starting a development server is an Execute action—it triggers an external operation whose effects (what services run, what ports are exposed, what code executes) depend on which server is started. Execute · High stop_server Stopping a server is an Execute action that triggers external operations (process termination) whose effects depend on which server argument is provided. Execute · High browser_click Browser click actions trigger UI interactions that can cause state changes, form submissions, navigation, or other side effects depending on what is clicked.

6 of DevServer MCP's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control DevServer MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and DevServer MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "browser_console_messages": {
    "limits": [
      {
        "counter": "browser_console_messages_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register DevServer MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DEVSERVER →

Instant setup, no code required.

FULL CATALOGUE

All 11 DevServer MCP tools

EXECUTE 6 tools

Execute browser_click browser_click Execute browser_navigate browser_navigate Execute browser_resize browser_resize Execute browser_type browser_type Execute start_server start_server Execute stop_server stop_server

READ 5 tools

Read browser_console_messages browser_console_messages Read browser_screenshot browser_screenshot Read browser_snapshot browser_snapshot Read get_devserver_logs get_devserver_logs Read get_devserver_statuses get_devserver_statuses

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about DevServer MCP

Is the DevServer MCP server safe to use without restrictions? +

The DevServer MCP server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the DevServer MCP server expose? +

11 tools across 3 categories: Execute, Read, Write. 5 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on DevServer MCP? +

Register the DevServer MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every DevServer MCP tool call.

Deterministic rules across all 11 DevServer MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DEVSERVER →

Instant setup, no code required.

11 DevServer MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.