start_container

What start_container does on Proxmox MCP Server

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

This tool executes an operation that starts a container in Proxmox VE infrastructure. While not destructive (it's reversible via stop_container), it is an Execute action as it triggers a state change in external systems. Severity is medium because starting containers could impact services and resource allocation, but the blast radius is limited compared to destructive operations like deletion.

From the tool's definition Tool name 'start_container' and description 'Start a container' indicate execution of a container startup operation, which triggers external infrastructure changes whose effects depend on which container is targeted.

The rule that runs start_container safely

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

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

Questions about start_container