atomic-red-team-mcp

The server includes a critical `execute_atomic` tool that runs system commands, inherently posing a high security risk. However, it is disabled by default (`ART_EXECUTION_ENABLED=false`) with explicit warnings in the documentation. Input validation is implemented for file paths and technique IDs (e.g., in `read_atomic_document` and `query_atomics`) to prevent path traversal and malformed inputs. Authentication via a static bearer token is supported but disabled by default, which is a significant risk for remote deployments, especially if `execute_atomic` is enabled and the server listens on `0.0.0.0` (default host). Users must implement proper network isolation and authentication when deploying remotely with execution enabled.