auto_recover · Npm Dev MCP: Risk & Policy

WHAT IT DOES

What auto_recover does on Npm Dev

AI agents invoke auto_recover to trigger actions in Npm Dev. 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 auto_recover needs a policy

This tool executes a multi-step automated recovery workflow (health check → recovery → re-validation) which involves starting/stopping/restarting dev server processes. It doesn't simply read state or write data — it actively triggers external process execution. Misuse could restart wrong projects, consume ports, or cause service disruption across multiple projects, warranting high severity.

From the tool's definition 自動復旧を実行（ヘルスチェック→復旧→再検証）— 'auto_recover' triggers automated health-check, recovery, and re-validation sequences; it runs external processes and restarts dev servers as part of the recovery pipeline.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

auto_recover Rate-limited

auto_recover 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": {
    "auto_recover": {
      "limits": [
        {
          "counter": "auto_recover_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 Npm Dev, so you can run agents against it safely.

FAQ

Questions about auto_recover

What does the auto_recover tool do? +

MCPサーバーの自動復旧を実行（ヘルスチェック→復旧→再検証）. It is categorised as a Execute tool in the Npm Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on auto_recover? +

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

What risk level is auto_recover? +

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

Can I rate-limit auto_recover? +

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

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

auto_recover is provided by the Npm Dev MCP server (masamunet/npm-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.