pve_node_service_control
Start, stop, restart, or reload any systemd service on a Proxmox VE node. Dry-runs by default to prevent accidental disruption of critical services.
Instructions
MUTATION: start/stop/restart/reload a service on a PVE node. Dry-run by default — the PLAN flags lockout-class services (sshd/pveproxy/pvedaemon/pve-cluster/corosync/networking/ ...) as HIGH because stop/restart can sever the management plane or break quorum. There is NO auto-undo for a service control. confirm=True executes and returns {"status": "submitted", "result": } — poll that UPID with pve_task_status. Check current state first with pve_node_service_status.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| node | No | PVE node name; defaults to the configured node | |
| action | Yes | Control action: 'start', 'stop', 'restart', or 'reload' | |
| confirm | No | False (default) returns a dry-run PLAN only; True executes the service control | |
| service | Yes | systemd service name to control, e.g. 'pveproxy' or 'sshd' | |
| proximo_target | No | Which configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |