proxmox_configure_firewall
Configure VM-level firewall rules
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-configure-firewall.md
What proxmox_configure_firewall does on MCP Proxmox Server
AI agents use proxmox_configure_firewall to create or update resources in MCP Proxmox Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Proxmox Server environment.
Why proxmox_configure_firewall is rated Medium
This tool modifies firewall rules on Proxmox VMs, which is a Write operation—it creates or updates configurations. While firewall rule changes can have security implications if misconfigured, they are reversible (rules can be reconfigured or removed). The severity is high because incorrect firewall configuration could expose VMs to network attacks or break legitimate traffic flow, impacting infrastructure security.
From the tool's definition Tool name is 'proxmox_configure_firewall' and description states 'Configure VM-level firewall rules'. The verb 'configure' indicates modification of firewall settings, which are reversible configurations rather than irreversible deletions.
Attacks that exploit this kind of access
The rule that runs proxmox_configure_firewall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_configure_firewall, this is the rule to start with:
proxmox_configure_firewall 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 MCP Proxmox Server, apply this rule, and every proxmox_configure_firewall call is checked against it from then on.
Questions about proxmox_configure_firewall
Configure VM-level firewall rules. It is categorised as a Write tool in the MCP Proxmox Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_configure_firewall: 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 MCP Proxmox Server. Nothing to install.
proxmox_configure_firewall 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 proxmox_configure_firewall 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 proxmox_configure_firewall. 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.
proxmox_configure_firewall is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Proxmox Server, and thousands of servers like it.
This server
Across the catalogue