Security audit

Proxmox

Security checks for vulnerabilities and agentic risk

Overview

This Proxmox plugin needs review because guest commands can bypass its advertised destructive-operation safeguards, and SSH connections do not verify server identities.

Start with a read-only API token and keep SSH keys unavailable unless you intend to grant guest shell access. Use dedicated restricted accounts and client-side approvals. Leaving the destructive-operation flag unset does not prevent destructive guest commands or file overwrites. SSH host-key verification should be added before sensitive use.

SkillSpector

SkillSpector was not run because this plugin release contains no bundled skills.

Static analysis

Detected: suspicious.env_credential_access

Environment variable access combined with network send.

Critical

Code: suspicious.env_credential_access
Location: dist/cli.js:282
Evidence: const raw = process.env.PROXMOX_SSH_MAX_OUTPUT_BYTES;

Environment variable access combined with network send.

Critical

Code: suspicious.env_credential_access
Location: dist/index.js:222
Evidence: const raw = process.env.PROXMOX_SSH_MAX_OUTPUT_BYTES;

Environment variable access combined with network send.

Critical

Code: suspicious.env_credential_access
Location: dist/mcp-bin.js:224
Evidence: const raw = process.env.PROXMOX_SSH_MAX_OUTPUT_BYTES;

Environment variable access combined with network send.

Critical

Code: suspicious.env_credential_access
Location: dist/mcp-server.js:228
Evidence: const raw = process.env.PROXMOX_SSH_MAX_OUTPUT_BYTES;