// SCAN REPORT

DevTools MCP Server

14 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

4 can modify or destroy data

10 read-only

14 tools total

Community server · catalogue entry verified 29/06/2026

How to control DevTools MCP Server ↓

TOOL MAP

What DevTools MCP Server exposes to your agents

Read (10) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous DevTools MCP Server tools

Destructive · Low clear_browser_logs Clearing browser logs destroys existing log data that cannot be recovered. Execute · High restart_dev_server Restarting a development server executes an external operation that halts and restarts processes. Execute · High start_dev_server Starting a development server is an Execute-category action: it runs code/processes and initiates external operations. Execute · High stop_dev_server Stopping a development server is an executable action that terminates a running process.

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

POLICY

How to control DevTools MCP Server

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

Deny destructive operations

{
  "clear_browser_logs": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "check_dev_server": {
    "limits": [
      {
        "counter": "check_dev_server_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 DevTools MCP Server — 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 DEVTOOLS →

Instant setup, no code required.

FULL CATALOGUE

All 14 DevTools MCP Server tools

DESTRUCTIVE 1 tools

Destructive clear_browser_logs Clear browser logs

EXECUTE 3 tools

Execute restart_dev_server Restart a development server Execute start_dev_server Start a development server in the background and return immediately Execute stop_dev_server Stop a running development server

READ 10 tools

Read check_dev_server Check the status of a development server Read detailed_process_list Get detailed process information with CPU, memory usage Read discover_running_servers Discover and import existing development servers running on common ports Read find_process_url Find URL/port for a process by name Read get_browser_log_stats Get statistics about collected browser logs Read get_browser_logs Get browser console logs with filtering options. Returns logs from web applications running on localhost. Read get_server_logs Get logs from a development server Read kill_process Kill process by name or PID Read list_running_servers List all running development servers Read test_http_endpoint Test direct access to HTTP endpoint (debug tool)

EXPLORE

Related servers

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

FAQ

Questions about DevTools MCP Server

Can an AI agent delete data through the DevTools MCP Server MCP server? +

Yes. The DevTools MCP Server server exposes 1 destructive tools including clear_browser_logs. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the DevTools MCP Server MCP server expose? +

14 tools across 3 categories: Destructive, Execute, Read. 10 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on DevTools MCP Server? +

Register the DevTools MCP Server 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 DevTools MCP Server tool call.

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

ENFORCE POLICY ON DEVTOOLS →

Instant setup, no code required.

14 DevTools MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.