simulator_shutdown · Xclaude Plugin MCP: Risk & Policy

WHAT IT DOES

What simulator_shutdown does on Xclaude Plugin

AI agents invoke simulator_shutdown to trigger actions in Xclaude Plugin. 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 simulator_shutdown needs a policy

Shutting down a running simulator is an operational action that terminates a running process/environment. It is reversible (the simulator can be rebooted), so it is not Destructive, but it does trigger an external operation with real effects on the simulator's state, classifying it as Execute. Misuse could disrupt active development or testing workflows.

From the tool's definition Shutdown a running simulator

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulator_shutdown Rate-limited

simulator_shutdown 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": {
    "simulator_shutdown": {
      "limits": [
        {
          "counter": "simulator_shutdown_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 Xclaude Plugin, so you can run agents against it safely.

FAQ

Questions about simulator_shutdown

What does the simulator_shutdown tool do? +

Shutdown a running simulator. It is categorised as a Execute tool in the Xclaude Plugin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulator_shutdown? +

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

What risk level is simulator_shutdown? +

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

Can I rate-limit simulator_shutdown? +

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

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

simulator_shutdown is provided by the Xclaude Plugin MCP server (conorluddy/xclaude-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

simulator_shutdown is one line of Xclaude Plugin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →