Currently mongos only checks supportsReadConcern() for a command when it is received with snapshot level read concern, otherwise deferring the check to mongod. As mongos starts to make more decisions based on read concern (e.g. global snapshot timestamp selection) and for consistency of validation, we should consider always performing this check on mongos instead. This would require verifying / adding correct supportsReadConcern() definitions for each cluster command.