Heaven forbid someone introduce a popular feature into an internal tool. I do know the concern here, but it seems to miss the forest for the leaves on the trees.
Are you going to assume ownership of that change if it breaks in production at any point and the team needs to provide support? Because I surely don't like owning pieces of critical code that wasn't implemented/explicitly maintained by my team, doing code archeology while putting out fires caused by 3rd parties' code is in the not-so-much-fun category of work.
You mean just like when someone thought it was a cool feature to have JNDI lookups in Log4J ?
At scale, if you let everyone do this, suddenly you're maintaining 50 features that were contributed and are each used by...two teams. Ownership with contributions requires really strong culture. (this is the same reason that you don't always see a PR just approved to an open source library.)