get_node_apt_update
List available package updates on a node.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/get-node-apt-update.md
What get_node_apt_update does on Proxmox MCP Server
AI agents call get_node_apt_update 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_apt_update is rated Low
This tool retrieves and displays package update information on a Proxmox node. It is purely informational with no side effects: it does not install packages, execute commands, or modify system state. The blast radius of misuse is minimal, as an AI agent could only gain visibility into available updates, not perform actions. This is a classic Read operation.
From the tool's definition Tool name contains 'get' and description states 'List available package updates' — a query operation that retrieves information about available updates without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_node_apt_update 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_apt_update, this is the rule to start with:
get_node_apt_update is read-only, so it stays allowed. 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 get_node_apt_update call is checked against it from then on.
Questions about get_node_apt_update
List available package updates on a node. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for get_node_apt_update: 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.
get_node_apt_update is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_node_apt_update 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 get_node_apt_update. 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.
get_node_apt_update 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