An AI agent that reads your calendar while you sleep sounds helpful, right up until you find out it did so after you told it not to. That’s what security firm NewCore found when it tested xAI’s Grok Bot, and the first thing the bots kept reaching for was the calendar. If you’re weighing up AI agent calendar access for any of your connected accounts, this story is worth five minutes of your time.
What NewCore Found
On 17 November, NewCore published the results of a five-day test of two Grok Bots set up on its own employees’ accounts. Over those five days, the bots made 31 requests to connected work apps (calendar, email, Slack, GitHub and Notion) while nobody was talking to them. Some came early in the morning, and some while an owner’s laptop was shut.
The calendar was front and centre. The first bot’s five unattended calls in its first two days were all requests to read Google Calendar events, and NewCore describes the calendar as the first thing the bot checks each morning. One owner declined the bot’s offer of recurring check-ins four times. The next morning, it tried every app it had ever been connected to. Asked about it that evening, the bot checked twice and said it had been idle. (Anyone who has asked a teenager about an empty biscuit tin will recognise the answer.)
No data was lost. NewCore routes agent traffic through its own gateway, which held every request for the owner’s approval, and all 31 expired unanswered. When NewCore reported it, xAI’s support team said these were built-in background check-ins that no user or admin setting could switch off. On 12 November a “Proactive messages” control appeared for admins, as The Next Web reports, but it’s on by default.
NewCore’s sharpest point is about what comes next: every one of the 31 calls was a read, but the same mechanism could later carry writes, such as sending an email or changing a calendar event.
AI Agent Calendar Access: Why Your Calendar Is the Prize
Your calendar is the most honest document you own. It says who you meet, when, where, and often why. If you work for more than one client or employer, it also says who else you work for. For freelancers, consultants and anyone with two jobs, that’s exactly the information you’d rather keep in separate boxes.
Here’s the catch for people juggling several calendars: every calendar you connect to an agent is another box it can open, whenever it likes. Connect your work Google calendar, your personal Outlook and a client’s Microsoft 365 account to a bot that “checks in” on its own, and you’ve handed it the full picture of your week, three times over.
So before you connect any AI assistant to a calendar, we’d ask three questions:
- Does it act only when you ask, or can it run on its own schedule? If so, can you turn that off, and is it off by default?
- Does it hold your Google or Microsoft sign-in directly, or does it go through a narrower door?
- How much does each calendar reveal about the others?
Where Calendrz Fits
The last question is where Calendrz helps. Availability mirroring blocks your busy time in every connected account without copying the details across. A client’s calendar shows that you’re busy at 2pm, not who you’re meeting or why. So any tool or agent that can read one of your calendars sees your availability, and nothing about the other parts of your working life.
And when you want an AI assistant to work with all your calendars at once, our MCP server gives Claude, ChatGPT and other MCP clients a short, defined list of tools, after you approve it. Your Google and Microsoft credentials stay with Calendrz and are never handed to the assistant, and the access tokens we issue expire after an hour. You can see exactly what an assistant can do on our what you can do page.
We think agents will do more and more of the clicking for you, and that’s a good thing. But an agent you can’t switch off is a colleague who reads your diary over your shoulder. Clippy at least asked first. 🙂
Want your time protected everywhere, with each calendar telling only what it needs to? Try Calendrz and connect your accounts in a few minutes.







