Datetime fields the lesser than operator is behaving as upper bound inclusive

For Task entity, I am checking for “create_at” and “modified_at” datetime fields the lesser than operator is behaving as upper bound inclusive.

The observation is when hitting Task search API URL(workspaces/{workspace_gid}/tasks/search) with the following filter-criteria -: created_at.before=2023-07-02T00:00:00.000Z, then the response data contains data with created_at=2023-07-02T00:00:00.000Z as well. It this the expected behavior ?