Read what you wrote yourself.
The idea of the program is to control the computers at a distance.
More carefully now.
Control computers remotely.
Your personal settings for virus have not been updated successfully.
Your program is made up of parts. One of them guarantees unrestricted control of a machine. What guarantees that other parts can not be used to capture text from password fields in browsers, for example? Or search for images and transmit them to any server? Or encrypt files against the will of the user, and only encrypt them by remote command? etc., etc., enter the malware behavior of the time here.
Then you think of some program that actually allows you to operate a computer through the network, such as Team Viewer, or the Windows Remote Desktop itself. In these cases you "authenticate" your program to use a user account, and this account must be "manipulated" in real time. The scope of what you can do in this way is very limited, but so even safer. Perhaps, to achieve your goal, you should study the architecture of these programs. Then you can do something similar. But that's not remote control.
Another simpler idea: Maybe you can solve your problem with a client-server architecture. Rather than creating an end-to-end remote control program, create services that can be installed locally on the machines and perform certain actions within a limited scope. You can have these services service requests over multiple network protocols. You can also compartmentalize your features by service, so it's easy to control the authorization of what each one can do. But that's still not remote control, okay?
