Current state for making changes to standard segments in FME means adding new keys to the definition either a) manually or b) via csv for convenience. If I want to include some sensitive data like unhashed phone numbers, emails, etc. in my segment, I am fully enabled to do so.

The desired state would be expanding the current OPA use in Harness to cover this surface. I should be able to enforce that inputs (whether they come from a keyboard or csv) to a segment have to pass a policy check. I should be able to block adding keys that match a certain banned shape. The initial use case is blocking username@domain.com (email-shaped) and 555-555-5555 (phone number shaped) keys, but can be reversed or expanded to block anything other than uids or other standardized shapes.

This should be an easy implementation as the event is already there to listen to/trigger a policy check, only the input data of the keys being added/changed/etc are missing.