I would like to confirm that a third-party library uses the correct write concern when sending commands to the MongoDB instance. There currently does not seem to be a way to do that.

Proposed solution: Make the database profiler store the write concern of each operation in the database's system.profile collection when the profiling level is set to 2.