No; the only reason Cmd would block a tool from running is if that tool were violating one of your Cmd Control triggers. Assuming properly-defined triggers, there will be no interference with remote server operation at all.

If you discover that one of your triggers blocks a tool, you can either redefine the trigger in a manner that doesn’t compromise the integrity of your security, or perform a cost-benefit analysis of removing the trigger for convenience if this blockage is severely impacting your internal operations.

Did this answer your question?