restart_explorer

SERVERNitrostack SOURCEnitrocloudofficial/nitrostack

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nitrostack/restart-explorer.md

WHAT IT DOES

What restart_explorer does on Nitrostack

AI agents invoke restart_explorer to trigger actions in Nitrostack. 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.

RISK

Why restart_explorer is rated High

Restarts critical OS process; disruptive but generally recoverable, requires confirmation.

From the tool's definition Restarts Windows Explorer process, system-level operation with side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs restart_explorer safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restart_explorer, this is the rule to start with:

restart_explorer Rate-limited

restart_explorer 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": {
    "restart_explorer": {
      "limits": [
        {
          "counter": "restart_explorer_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every restart_explorer call is checked against it from then on.

FAQ

Questions about restart_explorer

What does the restart_explorer tool do? +

Restarts the Windows Explorer process (windows.exe / taskbar / file explorer). Fixes a frozen taskbar, unresponsive Start menu, or ghost icons without a full reboot — a classic tech-support trick. Requires confirm:true — call once first to preview.. CRITICAL: Never output. It is categorised as a Execute tool in the Nitrostack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on restart_explorer? +

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

What risk level is restart_explorer? +

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

Can I rate-limit restart_explorer? +

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

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

restart_explorer is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nitrostack, and thousands of servers like it.

This server

All 697 Nitrostack tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →