proxmox_stop_lxc

A execute tool on the MCP Proxmox MCP server.

SERVERMCP Proxmox Server SOURCEbsahane/mcp-proxmox

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-stop-lxc.md

WHAT IT DOES

What proxmox_stop_lxc does on MCP Proxmox Server

AI agents invoke proxmox_stop_lxc to trigger actions in MCP Proxmox 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.

RISK

Why proxmox_stop_lxc is rated High

Stopping an LXC container is an Execute action because it runs/triggers an external operation (container halt) whose effects depend on which container is targeted. While not destructive (the container persists), it interrupts services and affects system state irreversibly in the short term, making it Execute rather than Write.

From the tool's definition Tool name 'proxmox_stop_lxc' indicates stopping/halting an LXC container in Proxmox virtualization infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs proxmox_stop_lxc safely

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

proxmox_stop_lxc Rate-limited

proxmox_stop_lxc 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": {
    "proxmox_stop_lxc": {
      "limits": [
        {
          "counter": "proxmox_stop_lxc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Proxmox Server, apply this rule, and every proxmox_stop_lxc call is checked against it from then on.

FAQ

Questions about proxmox_stop_lxc

What does the proxmox_stop_lxc tool do? +

proxmox_stop_lxc is a execute tool on the MCP Proxmox Server MCP server. It is categorised as a Execute tool in the MCP Proxmox 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 proxmox_stop_lxc? +

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

What risk level is proxmox_stop_lxc? +

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

Can I rate-limit proxmox_stop_lxc? +

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

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

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

KEEP EXPLORING

More on MCP Proxmox Server, and thousands of servers like it.

This server

All 124 MCP Proxmox Server tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →