get_node_firewall_log

Get firewall log for a node.

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/get-node-firewall-log.md

WHAT IT DOES

What get_node_firewall_log does on Proxmox MCP Server

AI agents call get_node_firewall_log 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 get_node_firewall_log is rated Low

This tool retrieves and queries firewall log information from a Proxmox node. It performs a read-only operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal - an attacker could gain visibility into firewall events but cannot alter infrastructure, trigger operations, or cause harm beyond information disclosure.

From the tool's definition Tool name contains 'get' and description states 'Get firewall log' - a retrieval operation. Returns existing log data with no side effects or modifications.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_node_firewall_log Allowed

get_node_firewall_log 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": {
    "get_node_firewall_log": {}
  }
}

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 get_node_firewall_log call is checked against it from then on.

FAQ

Questions about get_node_firewall_log

What does the get_node_firewall_log tool do? +

Get firewall log for a node. 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 get_node_firewall_log? +

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

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

Can I rate-limit get_node_firewall_log? +

Yes. Add a rate_limit block to the get_node_firewall_log 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 get_node_firewall_log completely? +

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

get_node_firewall_log 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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