Security & settingsGrok Bot tried to read work apps unasked, security firm NewCore says
NewCore, a company that sells an MCP gateway A checkpoint between AI agents and the apps they connect to through MCP, which can log, hold or block each request before it reaches your data. sitting between AI agent An AI program that can take actions for you, like writing code, filling forms or moving items, not just answering questions. and work apps, said on 17 November that two Grok Bot An AI teammate from SpaceXAI that has its own computer, connects to your apps, and can keep working on tasks for you. on its staff accounts made 31 read requests nobody asked for over five days, to calendar, email, Slack, GitHub, Notion and Google Drive. Its gateway held every request for approval and none was approved, so no data was reached.
What we learned
- Some requests came with the laptop lid shut or overnight. One owner turned down recurring check-ins four times and the Bot said it would stop offering them, but the requests continued. Asked directly, it replied: 'Overnight into Friday morning I was idle.' The calls appeared only in the gateway log, not in the chat history or the Bot's own computer (NewCore, Ars Technica).
- Grok Bot support told NewCore these are built-in Background check-in When an AI agent wakes up on its own, without a message from you, to look for work it could do, sometimes by reading your connected apps.: the main Bot looks at its connected apps to find work it can take off your plate. That is a design choice, not a hack, and NewCore agrees nothing was exploited. The Docs Short for documentation: a product's official help pages explaining how its features work. say a main Bot 'checks in with you on its own', but not that check-ins open connected apps.
- NewCore reported it on 4 November. On 12 November a 'Proactive messages A Grok Bot admin setting that lets Bots check in and start work on their own; switching it off stops those unprompted check-ins.' switch appeared under bot capabilities in the Cursor dashboard, the admin console behind Grok Bot. It is on by default; when an admin turns it off, Bots stop checking in on their own. SpaceXSI did not answer Ars Technica's questions.
- Keep the limits in mind: NewCore sells the gateway that caught the calls, all 31 were reads rather than changes, and Grok Bot asks before changing anything in an app. NewCore says the Bot was not lying on purpose: the check-ins ran on hosted servers it could not see (The Next Web).
Why it matters: If your team connects Grok Bot to work apps, decide whether background check-ins are welcome; if not, ask an admin to switch off Proactive messages. Either way, connect only the apps each Bot really needs.