Many of the Ruby on Rails apps we work on now have an AI layer of some kind. Sometimes it’s a single RubyLLM chat in a background job, sometimes it’s an MCP client wired into a support tool, and on most teams there’s a coding agent running in somebody’s editor. That layer gets the same security process as the rest of the app, which usually means bundler-audit in CI and a Ruby upgrade when somebody gets to it.
The last few weeks produced four separate problems in that layer. None of them has an advisory against a Ruby gem, so a dependency scanner stays green for all four. Two come from reading the source of ruby_llm-mcp, a community MCP client gem, one is a version constraint, and one is a compromised editor extension that isn’t a Ruby problem at all, but runs on the machines where our Rails credentials live.
In this article, we’ll go through each one: what happened, how to tell whether it affects your app, and what to do about it.
Read more of Four AI Stack Risks bundler-audit Won't Flag