#29416 [Bug]: Guardrail policies are not being saved to the db from config
### Check for existing issues
- [x] I have searched the existing issues and checked that my issue is not a duplicate.
### What happened?
When creating a guardrail policy and attachment in the config file they are not saved in the database and are also being overwritten by the empty database. Making us have to use supported_db_objects to exclude the policies from being loaded in and overwriting the config policies.
### Steps to Reproduce
1. Create a policy in your config file 2. Run your LiteLLM instance 3. Check the db/ui to see that no policies have been created
### Relevant log output
```shell [92m12:09:31 - LiteLLM Proxy:INFO[0m: init_policies.py:133 - Initializing 1 policies... [94m - politiegpt_guardrails[0m [92m12:09:31 - LiteLLM Proxy:INFO[0m: attachment_registry.py:67 - Loaded 1 policy attachments guardrails.add: ['example-validation'] [92m12:09:31 - LiteLLM Proxy:INFO[0m: init_policies.py:179 - Successfully loaded 1 policies
[92m12:09:31 - LiteLLM Proxy:INFO[0m: init_policies.py:190 - Successfully loaded 1 policy attachments [93mPolicy Attachments: 1 attachment(s)[0m [92m12:09:31 - LiteLLM Proxy:DEBUG[0m: attachment_registry.py:59 - Loaded att…