mcp-screenshot

The server uses `child_process.exec` to run platform-specific commands (e.g., `screencapture` on macOS, `import`/`grim` on Linux, `powershell.exe` on Windows/WSL) for screen and window capture. While necessary for its functionality, direct execution of external commands introduces an inherent risk of command injection if input is not meticulously sanitized. The `SecurityManager` implements robust path validation to prevent unauthorized file access and path traversal for save operations, and it includes rate limiting. The PowerShell scripts for Windows/WSL engines attempt to escape special characters, mitigating some injection vectors. Docker deployment includes `no-new-privileges` and non-root execution, which are good practices. However, the conditional `ENABLE_VNC` flag exposes port 5900, which can be a network risk if enabled in production. Overall, while conscious security efforts are made, the reliance on external command execution for core functionality means a moderate inherent risk.