Cloud:
Ensure the role assigned to the mms-automation includes the bypassDefaultReadMaxTimeMS privilege.
Expose the privilege bypassDefaultReadMaxTimeMS to be set via an Atlas UI (directly from the doc)
Users can view and set defaultReadMaxTimeMS via the Atlas UI and API (ensure users cannot set these via command)

Description of Linked Ticket

Summary

MongoDB will deliver a new feature, Server-Side Default maxTimeMS, where users can specify a server-side time limit for all operations.

Motivation

With 8.0, we will deliver a more adaptive experience to high-stress workloads. MongoDB will slow down stressful workloads and expensive operations through mechanisms like load shedding, queueing, and deprioritization. This will delay and minimize the impact of cluster-wide degradation. Notably, these are improvements that will not need user configuration; all users will see benefits upon upgrading to 8.0. 

While these features will improve database behavior upon reaching an unhealthy state, we must introduce capabilities that make it harder for customers to introduce problematic workloads in the first place. We must introduce something DBA-like users can enable as a “guardrail” against unintentionally expensive operations. This functionality is offered by some competitors, is an expectation from administrators, and has been requested by scores of Top-MRR customers for nearly a decade. MongoDB offering this functionality will enable customers to prepare their production workloads for success against unintentional failure - a necessity for our target, mission-critical customers.

Documentation

Product Description
Scope
Technical Design
Docs Update