Skip to main content
Glama

pve_sdn_vnet_firewall_rule_update

Update a SDN vnet firewall rule at a specific position, modifying only the fields you provide, with optional dry-run to preview changes before applying.

Instructions

MUTATION (LIVE/IMMEDIATE): update a vnet firewall rule at position pos. Dry-run by default — the PLAN shows the rule's current state and the fields changing. RISK_MEDIUM floor. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

Takes effect on live guest traffic THE INSTANT you confirm — no pve_sdn_apply gate, no pve_sdn_rollback coverage. Positions SHIFT after inserts/deletes — re-list before updating. Only the fields you pass are changed (unless moveto is given — see its own description). UNLIKE the guest/cluster/node firewall family, this endpoint's reads never expose a digest (schema-verified) — the PLAN's captured rule is best-effort identity evidence only, not an optimistic lock; supply digest ONLY if you have one from out-of-band, and confirming with none (the default) is the normal, supported path. No UNDO — revert by updating it back, or remove it with pve_sdn_vnet_firewall_rule_remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logNoNew log level; omit to leave unchanged.
posYesRule position (0-based index) to update.
destNoNew destination address/CIDR/alias; omit to leave unchanged.
vnetYesSDN vnet name.
dportNoNew destination port/range; omit to leave unchanged.
ifaceNoNew interface name; omit to leave unchanged.
macroNoNew macro name; omit to leave unchanged.
protoNoNew IP protocol; omit to leave unchanged.
sportNoNew source port/range; omit to leave unchanged.
actionNoNew rule action; omit to leave unchanged.
digestNoOPTIONAL optimistic-lock passthrough, forwarded verbatim when given. NEVER required, NEVER derived: this endpoint's reads (rules list / rule get) expose no digest field on this schema at all (schema-verified), so the PLAN cannot supply one — pass a digest only if you obtained one out-of-band.
enableNoNew enabled state; omit to leave unchanged.
movetoNoMove the rule to this new position instead — PVE IGNORES every other argument in this same call when moveto is given (schema-documented). Do the move and the field edit in two separate calls if you need both.
sourceNoNew source address/CIDR/alias; omit to leave unchanged.
commentNoNew free-text comment; omit to leave unchanged.
confirmNoSet True to execute the mutation; False (default) only returns a dry-run PLAN.
fw_typeNoNew rule type: in/out/forward/group; omit to leave unchanged.
icmp_typeNoNew ICMP type; omit to leave unchanged.
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
Behavior4/5

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

With no annotations, the description carries the full burden and covers most behavioral traits: mutation type, immediate effect, no rollback, no apply gating, digest behavior, and position shifting. Lacks explicit error handling details but is otherwise thorough.

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?

The description is detailed and well-structured, starting with the core purpose then expanding on behavior and constraints. Every sentence adds value, though a few repetitions (e.g., 'schema-verified') could be trimmed slightly.

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?

Covers purpose, behavior, side effects, parameter nuances, and related tools (pve_sdn_apply, pve_sdn_rollback, pve_sdn_vnet_firewall_rule_remove). Output schema exists, so return values are handled. Only minor omission is explicit error handling, but overall very complete.

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 the description adds significant value: explains dry-run/confirm mechanism, digest semantics (never required, never derived), and moveto's exclusive behavior. Clarifies that only passed fields are changed, which the schema does not convey.

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 'update a vnet firewall rule at position pos', specifying the verb and resource. It distinguishes from siblings like rule_add, rule_remove, and rules_list by emphasizing the update action and position-based semantics.

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?

Provides explicit guidance: dry-run by default, confirm to execute, risk level, synchronous behavior, immediate effect without apply gate, position shifts after changes, and alternatives like revert or remove. Also warns about special cases like moveto overriding other parameters.

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