There is as when it creates the config file a message is provided.
The error itself is very easy to fix with a permissions change and would occur with any type of program that happens to create a config file in a user's home directory for the first time.
Lots of things in play here and a general "don't do that" type scenario.
You can't always stop a user from doing something strange.
The old "sudo rm -rf /*" always comes to mind as any admin has always deleted something that they didn't mean to regardless of any warning or other scenario.