mittwald_container_stop

What mittwald_container_stop does on Mittwald MCP Server

AI agents invoke mittwald_container_stop to trigger actions in Mittwald 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 mittwald_container_stop is rated High

Stopping a container is an Execute action—it runs an external operation with effects that depend on the provided arguments (container ID/name). While not immediately destructive (the container can be restarted), it causes service disruption and fits the Execute category. The high severity reflects that an AI agent could maliciously stop production containers, causing availability loss.

From the tool's definition Tool name is 'mittwald_container_stop' and description states it will 'Stop a running container.' This triggers an external operation (stopping a container) whose effects depend on which container is specified as an argument.

The rule that runs mittwald_container_stop safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mittwald_container_stop": {
      "limits": [
        {
          "counter": "mittwald_container_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about mittwald_container_stop