I want to emphasize the real need for a fully independent “Auto-Run MCP” control, separate from the global “Auto-Run Mode”. Right now, when I disable “Auto-Run Mode”, all automations are turned off (MCPs included). And when I enable the global auto-run just to allow MCPs, I end up bringing along every other automated behaviors (command execution, file writes, linters, etc..). So, the only related option today is the “MCP Tools Protection” checkbox, but it only blocks MCPs once the general auto-run is active. In other words, it doesn’t solve our use case of wanting to keep only MCP auto-run enabled without activating full auto-run.
What you raised is exactly the point. I think we need a standalone “Auto-Run MCP” toggle outside of “Enable auto-run mode,” with the ability to whitelist by URL or server.