get_node_journal

What get_node_journal does on Proxmox MCP Server

AI agents call get_node_journal 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.

Why get_node_journal is rated Low

The tool appears to query or retrieve journal entries (system logs) from a Proxmox node without modifying infrastructure or performing side effects. While the description is empty, the semantic meaning of 'get_node_journal' strongly indicates a read operation. Confidence is reduced due to the lack of explicit description, but the naming convention is sufficiently clear to classify as Read with low severity.

From the tool's definition Tool name 'get_node_journal' indicates retrieval of system journal/log data from a Proxmox node. The prefix 'get_' and absence of modification keywords suggest read-only access to existing logs.

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

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

Questions about get_node_journal