What changed
Grok Bot 1.2.3 adds Always allow, Auto-review, Needs approval and Blocked settings per connector tool, team limits for GitHub tools, reconnect cards and paused scheduled runs when connector sign-in expires. It also separates personal, organization, instruction and project memories.
Why it matters
Tool-level grants and fail-closed schedules reduce the chance that a broad connector or expired credential silently extends an agent’s authority, but the new settings add more policy layers that must agree.
What to do
Set one connector tool to each permission state, expire its sign-in during a routine, and verify the run pauses, notifications arrive, memory remains scoped and team policy overrides personal MCP configuration.
Caveat
Several controls require minimum Grok Bot versions and Teams or Enterprise plans. xAI’s changelog is implementation evidence, not an independent permission or memory-isolation audit.