pve_start_container · Proxmox MCP Server MCP: Risk & Policy

WHAT IT DOES

What pve_start_container does on Proxmox MCP Server

AI agents invoke pve_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 IT NEEDS A POLICY

Why pve_start_container needs a policy

This tool executes an operation that changes system state by launching a container. While not destructive or financial, it clearly triggers an external operation (container startup) that can have cascading effects on system resources, network, and dependent services.

From the tool's definition Tool name 'pve_start_container' and description 'Start a container' indicate execution of a containerized workload. Starting a container triggers external operations whose effects depend on runtime arguments (which container, with what configuration).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pve_start_container Rate-limited

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

FAQ

Questions about pve_start_container

What does the pve_start_container tool do? +

Start a container. It is categorised as a Execute tool in the Proxmox 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 pve_start_container? +

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

What risk level is pve_start_container? +

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

Can I rate-limit pve_start_container? +

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

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

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