Skills-MCP-Veeam-Backup-Pro

The server's default configuration, especially in `docker-compose.yml` and explicitly in several tool files, sets `VEEAM_IGNORE_SSL` to `true` or `rejectUnauthorized` to `false`. This disables SSL certificate validation for connections to the Veeam REST API, making the communication vulnerable to Man-in-the-Middle (MITM) attacks. While `SafetyGuard` is implemented for critical write operations (`start-backup-job`, `stop-backup-job`) requiring explicit confirmation tokens and audit logging, and sensitive credentials are sourced from environment variables, the default insecure SSL configuration is a critical vulnerability for production environments. The HTTP server runs without native HTTPS, relying on external reverse proxy for SSL in production, which is a documented but insecure default for direct exposure.