Skip to main content
Glama

pve_sdn_vnet_firewall_rule_add

Add a new SDN vnet firewall rule that takes effect instantly on live guest traffic. Dry-run to preview; confirm to apply. Actions: ACCEPT, DROP, REJECT. Misplaced rules can sever traffic immediately with no undo.

Instructions

MUTATION (LIVE/IMMEDIATE): add a new vnet firewall rule. Dry-run by default — the PLAN shows vnet, type, action, and key address/port fields. RISK_MEDIUM floor (absence of HIGH is NOT a safety signal). Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

UNLIKE the shipped guest/cluster/node pve_firewall_rule_add (always inserts at position 0), this takes effect on live guest traffic THE INSTANT you confirm — no pve_sdn_apply gate, no pve_sdn_rollback coverage. A misplaced DROP/REJECT can sever traffic for every guest on this vnet immediately. No UNDO — revert by removing it with pve_sdn_vnet_firewall_rule_remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logNoLog level for this rule, e.g. 'info', 'nolog'.
posNoPosition to insert at — Smoke-confirm: this endpoint's schema declares 'pos' on CREATE with description text copy-pasted from its PUT sibling; actual create-time effect (insert-at-pos vs. append vs. ignored) is unconfirmed.
destNoDestination address/CIDR/alias to match, or None for any.
vnetYesSDN vnet name.
dportNoDestination port or port range to match, e.g. '22' or '8000:8010'.
ifaceNoNetwork interface name to match.
macroNoPredefined standard macro name.
protoNoIP protocol to match, e.g. 'tcp', 'udp', 'icmp'.
sportNoSource port or port range to match.
actionYesRule action: 'ACCEPT', 'DROP', or 'REJECT'.
digestNoOptimistic-lock digest — schema-declared on this endpoint's CREATE (a platform inconsistency vs. the shipped guest/cluster/node rule_add, which accepts none); forwarded when given.
enableNoWhether the rule is active immediately; omit to use PVE's own default (enabled).
sourceNoSource address/CIDR/alias to match, or None for any.
commentNoFree-text comment stored with the rule.
confirmNoSet True to execute the mutation; False (default) only returns a dry-run PLAN.
fw_typeNoRule type: 'in', 'out', 'forward', or 'group' (richer than the guest/cluster/node firewall's in/out-only direction).in
icmp_typeNoICMP type, only valid when proto is icmp/icmpv6/ipv6-icmp.
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 live/immediate effect, synchronous behavior, no task UPID, dry-run default, risk medium floor, and absence of undo. Also notes schema inconsistency for 'pos' parameter.

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

Conciseness5/5

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

Efficiently structured with purpose, behavior, warnings, and comparisons. Every sentence adds critical information without redundancy.

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 all key aspects: immediate effect, dry-run, confirmation, risk, undo mechanism, output format, and comparison with similar tools. Suitable for an agent to invoke correctly.

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

Parameters4/5

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

Schema has 100% description coverage, so baseline 3. Description adds value by explaining the confirm parameter's role and the uncertain behavior of 'pos', but does not detail other parameters beyond schema.

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?

Clearly states 'add a new vnet firewall rule' with verb and resource. Differentiates from sibling tools by noting behavioral differences in position handling and immediate effect.

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 when-to-use (add vnet rule), dry-run vs. confirm, risk level, and comparison with sibling tools. Warns about no undo and recommends removal tool for revert.

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