disable_cluster_time_gossiping_in_unreadable_state.js intentionally sends an invalid cluster time and does so by changing the timestamp of a received valid cluster time. The valid time is taken from the response of a previous command so it is the same object captured by the session when processing that response. This leads the next command on that session to gossip the invalid time and can trigger an unexpected LogicalTimeMismatch error if a greater time has not already been validated by the server. To avoid this, the test should make a copy of the response's $clusterTime and modify that instead.