How can we ensure that when a user is granted only SELECT privileges, executing SELECT FOR UPDATE do

We are currently using Oracle 11.2.0.3, and recently, a developer unintentionally caused a large number of lock waits. Upon investigation, we found that the developer only had SELECT privileges on a specific table in the production database but mistakenly thought they were connected to the test database. As a result, they executed a SELECT FOR UPDATE, which placed a prolonged lock on the table, causing a significant number of sessions to experience lock waits.

To prevent such issues in the future, is there a way to ensure that SELECT FOR UPDATE cannot be executed or does not place locks when the user only has