Ability to disable remote MCP server access

What is the challenge?

Enterprise organizations with AI governance policies require all MCP server connections to go through an internal security review before production use. Aha! software currently has no way to disable the MCP server at the account level, leaving these customers unable to use the product in a compliant way until their review is complete.

What is the impact?

Enterprise accounts with strict AI governance requirements are blocked from using Aha! in production until this control exists. They have no workaround today.

Describe your idea

Add a toggle in Account settings > AI controls that allows account administrators to disable the Aha! MCP server for their account. When disabled, all active MCP connections are terminated immediately and no new connections can be established. When re-enabled, access is restored. Only account administrators can change this setting.