Re:Running Claude Code dangerously (safely)
by gregoriol on Tuesday January 20, 2026 @08:46AM
(#46691785)
Why in the hell would it be able to access a _remote_ database?! In no acceptable dev environment would someone be able to access that.
Re:Running Claude Code dangerously (safely)
by heartbreak on Tuesday January 20, 2026 @09:30AM
(#46692173)
Everywhere I’ve ever worked, there was always some way to access a production system even if it required multiple approvals and short-lived credentials for something like AWS SSM. If the user has access, the agent has access, no matter how briefly.
Re:Running Claude Code dangerously (safely)
by gregoriol on Tuesday January 20, 2026 @09:38AM
(#46692246)
Not if you require auth with a Yubikey, not if you run the LLM client inside a VM which doesn't have your private ssh key, ...
Re:Running Claude Code dangerously (safely)
by prodigycorp on Tuesday January 20, 2026 @09:29AM
(#46692165)
Supabase virtually encouraged it last year haha. I tried using it once and noped out after using it for an hour, when claude tried to do a bunch of migrations on prod instead of dev.
https://web.archive.org/web/20250622161053/https://supabase....
Now, there are some actual warnings. https://supabase.com/docs/guides/getting-started/mcp#securit...
There is definitely a real world risk. You should browse the ai coding subreddits. The regularity of `rm -rf` disasters is, sadly, a great source of entertainment for me.
I once was playing around, having Claude Code (Agent A) control another instance of Claude Code (Agent B) within a tmux session using tmux's scripting. Within that session, I messed around with Agent B to make it output text that made Agent A think Agent B rm -rf'd entire codebase. It was such a stupid "prank", but seeing Agent A's frantic and worried reaction to Agent B's mistake was the loudest and only time I've laughed because of an LLM.