list_firewall_macros

List available firewall macros (predefined rule sets like SSH, HTTP, etc.).

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/list-firewall-macros.md

WHAT IT DOES

What list_firewall_macros does on Proxmox MCP Server

AI agents call list_firewall_macros to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_firewall_macros is rated Low

This tool queries and returns data about existing firewall macros without side effects. It does not create, modify, delete, or execute any infrastructure changes. The blast radius of misuse is minimal—an AI agent obtaining this list cannot cause harm to the Proxmox VE environment.

From the tool's definition Tool name 'list_firewall_macros' and description 'List available firewall macros' indicate a read-only retrieval operation. The verb 'list' retrieves information about predefined firewall rule sets without modifying, executing, or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_firewall_macros 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 list_firewall_macros, this is the rule to start with:

list_firewall_macros Allowed

list_firewall_macros is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_firewall_macros": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every list_firewall_macros call is checked against it from then on.

FAQ

Questions about list_firewall_macros

What does the list_firewall_macros tool do? +

List available firewall macros (predefined rule sets like SSH, HTTP, etc.). It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_firewall_macros? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for list_firewall_macros: 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.

What risk level is list_firewall_macros? +

list_firewall_macros is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_firewall_macros? +

Yes. Add a rate_limit block to the list_firewall_macros 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.

How do I block list_firewall_macros completely? +

Set action: deny in the PolicyLayer policy for list_firewall_macros. 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.

What MCP server provides list_firewall_macros? +

list_firewall_macros 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.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →