secure-cluster-mcp

The server implements strong guardrails including strict path validation (`validate_remote_path`) to confine operations to `REMOTE_BASE_PATH`, a comprehensive blocklist (`DANGEROUS_PATTERNS`) for hazardous commands like `rm -rf`, and rate limiting to prevent cluster spam. A significant security concern is that `DRY_RUN` mode defaults to `False` in `src/secure_cluster_mcp/config.py`. This means the server will perform real cluster operations immediately upon launch unless the user explicitly sets `DRY_RUN=true` in their `.env`. While `CLAUDE.md` instructs AI agents to prioritize `DRY_RUN=true`, the application's default behavior is risky for first-time users or accidental deployments. The SSH client uses `paramiko.AutoAddPolicy()`, which automatically adds unknown host keys, a convenience that slightly reduces security compared to manual host key verification.