Back to skill

Security audit

Proxmox

Security checks for vulnerabilities and agentic risk

Overview

This Proxmox skill matches its infrastructure-management purpose, but it appears to enable disruptive VM, snapshot, delete, and backup operations without enough safety guidance or scoping.

Install only if you are comfortable giving the agent administrative control over Proxmox resources. Use a least-privileged API token, avoid broad shell-session credential exports where possible, protect any credential file, and require explicit human confirmation before shutdown, reboot, delete, rollback, or backup actions.

Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Lp3

Medium
Category
MCP Least Privilege
Confidence
94% confidence
Finding
The skill exposes shell-based operational capability but does not declare permissions or constraints, which weakens policy enforcement and user awareness around what the skill can execute. In a cluster-management skill that can start, stop, snapshot, and back up infrastructure, undeclared shell access materially increases the chance of unsafe or unauthorized actions.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The documented commands include destructive or high-impact operations such as stop, shutdown, reboot, snapshot rollback, and delete without any warning, confirmation, or safety preconditions. In infrastructure management, an agent following these instructions could cause downtime, data loss, or irreversible rollback from a casual or ambiguous user request.

Missing User Warnings

Low
Confidence
86% confidence
Finding
Starting backups is presented as a routine action without noting potential CPU, I/O, storage, and snapshot impact on production workloads. In a virtualization environment, initiating backups at the wrong time can degrade service or fill storage, especially if triggered automatically by an agent.

Session Persistence

Medium
Category
Rogue Agent
Content
---
name: proxmox
description: Manage Proxmox VE clusters via REST API. Use when user asks to list, start, stop, restart VMs or LXC containers, check node status, create snapshots, view tasks, or manage Proxmox infrastructure. Requires API token or credentials configured.
---

# Proxmox VE Management
Confidence
93% confidence
Finding
The skill instructs users to persist long-lived Proxmox API credentials in environment variables or a local credentials file and to source them into the shell session. Persistent admin infrastructure tokens increase exposure through shell history, process environment leakage, local file compromise, or accidental reuse by other tools and sessions.

Static analysis

No suspicious patterns detected.