stop_server · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_server does on Morpheus MCP Server

AI agents invoke stop_server 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 stop_server needs a policy

Stopping a server is an Execute action because it triggers an external operation (power-off) whose effects depend on which server is targeted. While not destructive (data persists and the action is reversible), it directly impacts infrastructure availability and operations.

From the tool's definition Tool name 'stop_server' with description 'Power off a server' indicates execution of a power management operation on infrastructure. This is an external operation with real-world effects on running systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_server Rate-limited

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

FAQ

Questions about stop_server

What does the stop_server tool do? +

Power off a server. 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 stop_server? +

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

What risk level is stop_server? +

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

Can I rate-limit stop_server? +

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

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

stop_server 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.