mittwald_container_stop · Mittwald MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why mittwald_container_stop needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mittwald_container_stop Rate-limited

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

FAQ

Questions about mittwald_container_stop

What does the mittwald_container_stop tool do? +

Stop a running container. It is categorised as a Execute tool in the Mittwald 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 mittwald_container_stop? +

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

What risk level is mittwald_container_stop? +

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

Can I rate-limit mittwald_container_stop? +

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

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

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