Why can an EDM user with no write permission change the parent in an in-flight request?

In our workflow, an EDM user that is an approver on an Approval Policy that includes Enrich access but does not have any write access permissions can change the parent in an in-flight request. The request then has a validation error as the user does not have the permission to make the change, but it still allows the action to "Change Parent" and cause that validation error. Is this expected behavior?