add_firewall_ipset_entry
Add an IP/CIDR to an IP set.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/add-firewall-ipset-entry.md
What add_firewall_ipset_entry does on Proxmox MCP Server
AI agents use add_firewall_ipset_entry to create or update resources in Proxmox MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxmox MCP Server environment.
Why add_firewall_ipset_entry is rated Medium
This tool creates or modifies firewall IP set entries, which are reversible changes to network access control rules. It does not delete data (Destructive), execute arbitrary code (Execute), or handle finances (Financial). However, misconfiguration could significantly impact network security and access policies across Proxmox infrastructure, warranting high severity.
From the tool's definition Tool description states 'Add an IP/CIDR to an IP set', which is a create/modify operation on firewall configuration.
Attacks that exploit this kind of access
The rule that runs add_firewall_ipset_entry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_firewall_ipset_entry, this is the rule to start with:
add_firewall_ipset_entry stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every add_firewall_ipset_entry call is checked against it from then on.
Questions about add_firewall_ipset_entry
Add an IP/CIDR to an IP set. It is categorised as a Write tool in the Proxmox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for add_firewall_ipset_entry: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Proxmox MCP Server. Nothing to install.
add_firewall_ipset_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_firewall_ipset_entry rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for add_firewall_ipset_entry. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
add_firewall_ipset_entry is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
This server
Across the catalogue