Person Number Auto-Generation Not Enforced for CW Creation via REST API

Hi,

We currently use manual Person Number generation, and our CWs are created via REST API by the SailPoint team (they pass the Person Number).
We are now enabling Automatic Person Number Generation.

Testing shows:

• UI correctly prevents entering Person Number (expected).
• REST allows creation without Person Number (expected).
• But REST still accepts a manually passed Person Number, even when auto-generation is enabled.

This creates a risk:
If SailPoint sends a Person Number that falls within the auto-generated sequence, it causes sequence conflicts and requires manual correction at enterprise level.

Request:

Is there any way to block REST API from accepting Person Number