Out of interest, why not create a database user account that is read only and use that?
Just to add some more thoughts based on other comments.. yes a lot of companies do stuff like this, particularly startups. The upside in these situations is that you end up learning things extremely quickly which wouldn't be possible in a more controlled environment. However not having backup and restore working is just ridiculous and I keep shaking my head at how they blamed the OP for this mistake. Unbelievable.
Or a coworker will find the login in your scripts, repurpose it, then notice they need more rights and "fix" the account for you.
SELECT * FROM my_200_GB_table will always be there.
It's actually quite nice using a database server that doesn't require explicit credentials to be used.