stop_dev_server · DevTools MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_dev_server does on DevTools MCP Server

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

Stopping a development server is an executable action that terminates a running process. It is not merely reading data (Read), nor is it creating/modifying data reversibly (Write). It is not permanently destructive in the sense of deleting files or data (Destructive), but it does execute a command with real operational consequences.

From the tool's definition Tool description states 'Stop a running development server' — this triggers an external operation (terminating a process) whose effects depend on which server argument is provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_dev_server Rate-limited

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

FAQ

Questions about stop_dev_server

What does the stop_dev_server tool do? +

Stop a running development server. It is categorised as a Execute tool in the DevTools 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 stop_dev_server? +

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

What risk level is stop_dev_server? +

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

Can I rate-limit stop_dev_server? +

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

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

stop_dev_server is provided by the DevTools MCP Server MCP server (shabaraba/devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.