Review what database credentials my app uses at runtime and scope them to least privilege. Check my connection config and how the database was set up. Apply these principles: the app should connect with a dedicated database user, not the superuser, root, or admin account; that user needs only the permissions the app uses (typically SELECT, INSERT, UPDATE, DELETE on the app's own tables or collections), not DDL like DROP or ALTER and not access to other databases on the same server; migrations run with separate, broader credentials used only at deploy time, not the runtime ones; and credentials come from environment variables, never from committed config. Do not change the database schema or any queries. If my host provisions a single all-powerful user by default (common on managed databases), show me how to create the scoped user with the provider's tooling or SQL. Keep a path for running migrations so deploys don't break. Deliver: the current permission state, the scoped setup you recommend with the exact commands or steps, and a verification: connect as the app's new user and confirm a DROP or cross-database query fails while normal app queries work.