Redefine Safety Context Tile.
Marking an app as unsafe seems to a bit too harsh, and I'd think an average user that isn't a developer would not understand the context, and would simply avoid the app all-together. This isn't fair towards the developers. One such example is Postman. It is marked unsafe simply because it uses a legacy system and can read/write data. But it's not unsafe...it's no more unsafe than a text editor.
When you install apps from the Android store (and perhaps the Apple Store, it's been a while since I've touched anything Apple), it simply notifies you about what permissions an app needs. I think that is all that the Safety tile should do...let the user decide how "unsafe" it is based on how comfortable they feel with the permissions.
That being said, the user should also understand why an app is requesting that permission. For example, a text editor needs read/write permissions because it needs to be able to save and load documents to/from local storage, store and retrieve settings from a file, and/or create log files for crashes and fault diagnostics.
If anything, unsafe term should be reserved for an outdated app or an app that has known security vulnerabilities. Personally, I do not like using/downloading ancient software that hasn't been updated close to a year or more.