I posted mine in a sibling comment before seeing yours--

I had a static code analysis tool (written in PHP for analyzing PHP code) crash on our codebase. Crash in this cause not being "seg faulted the interpreter" or something concerning, it just hit an invalid state internally, identified it, and cleanly exited with an error to let me know something was wrong. Got Claude to track down what was wrong and how our codebase was triggering it. I asked it to create a minimal reproduction I could include on my bug report, and the guard rails triggered and refused to answer. Asking Claude why that would happen, it suggested because what I was doing looked like exploit development.