Skip to main content
Glama

pve_sdn_vnet_firewall_options_set

Set firewall options for a Proxmox SDN vnet with immediate effect. Dry-run by default to review potential impact before confirming changes.

Instructions

MUTATION (LIVE/IMMEDIATE): set vnet firewall options. Dry-run by default — the PLAN shows current values and a DIRECTION-AWARE blast-radius warning. RISK_HIGH when enable or policy_forward changes, else MEDIUM. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

The HIGH-risk warning is derived from the actual values being set: tightening (enable= True, policy_forward=DROP) warns this can immediately CUT forwarded traffic; loosening (enable=False, delete=["enable"], policy_forward=ACCEPT) warns this immediately REMOVES firewall protection instead — the two are never conflated. An unrecognized/conflicting combination gets a combined warning covering both directions rather than guessing.

UNLIKE the staged zone/vnet/subnet SDN objects, this takes effect on live guest traffic THE INSTANT you confirm — there is no pve_sdn_apply gate and no pve_sdn_rollback coverage for this family. Requires at least one of options/delete. No UNDO — revert by setting the prior values back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vnetYesSDN vnet name.
deleteNoList of option keys to unset.
digestNoOptimistic-lock digest forwarded to PVE to abort if the options changed since a prior read.
confirmNoSet True to execute the mutation; False (default) only returns a dry-run PLAN.
optionsNoKey-value bag of options to set: enable (bool), log_level_forward, policy_forward (ACCEPT/DROP).
proximo_targetNoWhich 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
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses dry-run default, synchronous execution, result format, immediate effect, no rollback/undo, and detailed warning logic for tightening vs loosening. No annotations provided, so description fully covers behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is thorough but not overly verbose; uses clear labels and sections. Slightly long but every sentence adds value, so it earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the mutation complexity and presence of an output schema, the description explains return value, risk, and no-long-running-task behavior. It covers all essential context for invoking the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning beyond schema: explains delete as unsetting keys, digest as optimistic lock, confirm as execute flag, options key-value bag with accepted keys, and implicit requirement that at least one of options/delete is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sets vnet firewall options and distinguishes from siblings by emphasizing live/immediate mutation vs staged SDN objects. The verb 'set' and resource 'vnet firewall options' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides when to use (live mutation), when not to use (prefer staged objects), risk levels based on parameter changes, and states no UNDO. Also notes required parameters (at least one of options/delete).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server