300s indicate that client must take a follow-up action to fulfill the request. This would be misleading as the request is denied permanently.

Further, the closest match among the currently implemented statuses is a 403. As per the "Acknowledgements" section:

Thanks to Terence Eden, whose blog observed that the existing status code 403 was not really suitable for this situation, and suggested the creation of a new status code.