run_apt_update

Refresh the package index on a node (apt update).

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/run-apt-update.md

WHAT IT DOES

What run_apt_update does on Proxmox MCP Server

AI agents invoke run_apt_update to trigger actions in Proxmox MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_apt_update is rated High

This tool executes an external command (apt update) on a Proxmox node, which is an operation with side effects that depend on node state and network conditions. While not destructive (data is not irreversibly deleted) and not immediately dangerous in isolation, it triggers system-level operations that could affect infrastructure stability.

From the tool's definition Tool name 'run_apt_update' and description 'Refresh the package index on a node (apt update)' indicate execution of a system package management command that modifies node state and can trigger network operations and disk writes.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

run_apt_update Rate-limited

run_apt_update stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_apt_update": {
      "limits": [
        {
          "counter": "run_apt_update_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about run_apt_update

What does the run_apt_update tool do? +

Refresh the package index on a node (apt update). It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_apt_update? +

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

What risk level is run_apt_update? +

run_apt_update is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_apt_update? +

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

How do I block run_apt_update completely? +

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

What MCP server provides run_apt_update? +

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

KEEP EXPLORING

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

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →