restart_instance · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_instance does on Morpheus MCP Server

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

Restarting an instance executes a command on cloud infrastructure with real-world effects (downtime, service interruption, resource state changes). While not destructive or financial, it qualifies as Execute because it triggers external system operations whose consequences depend on the argument (instance_id). Misuse could disrupt production workloads.

From the tool's definition Tool performs 'restart an instance' action that triggers external infrastructure operation on HPE Morpheus appliance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_instance Rate-limited

restart_instance 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_instance": {
      "limits": [
        {
          "counter": "restart_instance_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 Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about restart_instance

What does the restart_instance tool do? +

Restart an instance. instance_id: from list_instances. It is categorised as a Execute tool in the Morpheus 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 restart_instance? +

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

What risk level is restart_instance? +

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

Can I rate-limit restart_instance? +

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

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

restart_instance is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

restart_instance is one line of Morpheus MCP Server'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 →