pve_firewall_set_enabled
Enable or disable the Proxmox firewall for a specified scope (cluster, node, guest). Dry-run by default—set confirm=True to apply. Use with caution as enabling may lock you out.
Instructions
MUTATION (HIGH RISK): toggle the firewall on or off for the given scope. Dry-run by default. RISK_HIGH both directions: enabling may instantly lock you out (default-DROP, no ACCEPT for 22/8006); disabling strips all protection. Cluster scope = master kill-switch. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.
This is the focused tool for just the enable flag; for policy/log-level/ebtables options use pve_firewall_options_set. No UNDO — re-toggle manually to revert.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Guest kind for scope='guest': 'qemu' or 'lxc'. | |
| node | No | Node name, required for scope='node' or scope='guest'. | |
| vmid | No | Guest VMID/CTID, required for scope='guest'. | |
| scope | No | Firewall scope: 'cluster', 'node', or 'guest'. | cluster |
| confirm | No | Set True to execute the mutation; False (default) only returns a dry-run PLAN. | |
| enabled | Yes | Desired firewall state: True to turn on, False to turn off. | |
| 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 |