Yeah, I think so. And you know, today is a world where we’re moving towards AI with connectors. So these are AI models that can plug in to your email, your Google Docs, your Slack. And I think that poses real risks. People today are fairly good at jailbreaking models, too, if there’s a very motivated hacker. So what is the implication, right?
Exact quote, beginning
Mark Chen
Chief Research Officer at OpenAI
Mark Chen said AI systems connected to email, Google Docs, and Slack could let a motivated attacker take information or launch a coordinated attack.
Chief Research Officer, OpenAIPublished June 25, 2025 · date of remarks not establishedTech Unheard podcast, Episode 7
Context and checks
Surrounding words
Rene Haas[13:26] Yeah. I don’t know how much you interface with potential clients, but do you hear the safety thing increasing, now, given with the capability of certainly [GPT-]4.5 and [OpenAI] o3? Mark Chen[13:35] Yeah, I think so. And you know, today is a world where we’re moving towards AI with connectors. So these are AI models that can plug in to your email, your Google Docs, your Slack. And I think that poses real risks. People today are fairly good at jailbreaking models, too, if there’s a very motivated hacker. So what is the implication, right? You could imagine that someone motivated extracts all that information away from you or they’re able to launch some kind of coordinated attack. Rene Haas[14:03] Right, so then literally at the source code level, you could just simply put things inside the model that when those queries are requested, be rejected. Mark Chen[14:12] Right. Yeah.
What this quote does not say
- The transcript says 'some kind of coordinated attack' without specifying the target, scale, or mechanism.
- Later in the interview, Chen described connected personal agents as desirable; he did not withdraw the connector risks stated here.
How this was checked
- Quote matched character-for-character against the captured page.
Reviewed by
an AI reviewer that read the whole source · an automatic character-by-character check