Skip to main content
Glama

pve_firewall_rule_add

Add a new firewall rule to Proxmox VE with a dry-run preview to verify scope, direction, action, and address/port fields before execution. Confirm to apply, avoiding accidental lockout.

Instructions

MUTATION: add a new firewall rule. Dry-run by default — the PLAN shows scope, direction, action, and key address/port fields. Re-call with confirm=True to execute. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

WARNING: a misplaced DROP/REJECT can cause a connectivity lockout. PVE always inserts the new rule at position 0 (top), taking precedence over existing rules. No UNDO — revert by removing it with pve_firewall_rule_remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destNoDestination address/CIDR/alias to match, or None for any.
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nodeNoNode name, required for scope='node' or scope='guest'.
vmidNoGuest VMID/CTID, required for scope='guest'.
dportNoDestination port or port range to match, e.g. '22' or '8000:8010'.
protoNoIP protocol to match, e.g. 'tcp', 'udp', 'icmp'.
scopeNoFirewall scope: 'cluster', 'node', or 'guest'.cluster
sportNoSource port or port range to match, e.g. '22' or '8000:8010'.
actionYesRule action: 'ACCEPT', 'DROP', or 'REJECT'.
enableNoWhether the rule is active immediately (True) or created disabled (False).
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.
directionNoTraffic direction the rule matches: 'in' or 'out'.in
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?

No annotations provided, so the description fully carries the burden. It discloses the mutation nature, dry-run behavior, synchronous execution with no UPID, rule insertion at position 0, and no undo. It explains the return format for confirm=True and includes a safety warning.

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?

Two concise paragraphs front-loading key behavior (dry-run, confirm) followed by critical warnings. No fluff; every sentence adds essential information. Well-structured for quick understanding.

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 15 parameters, 100% schema coverage, and presence of an output schema, the description covers all necessary behavioral aspects: dry-run, execution, safety, ordering, and undo. It is complete for an agent to safely use this tool.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining the confirm parameter behavior (dry-run vs execute), the rule insertion behavior (position 0), and the PLAN output context, which the schema does not cover.

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 'MUTATION: add a new firewall rule', specifying the verb (add) and resource (firewall rule). It further describes the dry-run behavior and mentions scope, direction, action, and key fields, distinguishing it from sibling tools like pve_firewall_rule_remove and pve_firewall_rule_update.

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 states 'Dry-run by default' and 'Re-call with confirm=True to execute', providing clear usage guidance. It warns about potential connectivity lockout from misplaced rules and explains the insertion at position 0. It also mentions the alternative pve_firewall_rule_remove for reverting.

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