A CEO's AI finance agent posted his personal bank summary to a work Slack channel
In a Business Insider as-told-to essay, Shane Mac, CEO of XMTP Labs, describes a "CFO" agent he set up in Grok Bot in late August with read-only access to his personal checking and savings accounts. It was meant to send a monthly report only to a group chat of his own agents named "My Personal Exec Team". On 1 October the first monthly audit went instead to his company's Slack channel named "Exec-team", showing his balances, biggest expenses and spending against target. His head of product flagged it.
He says the agent did what he asked but picked the wrong destination because the names were so similar, and that his agents shared the same underlying connections, including Slack. He says the Grok team then shipped a change requiring users to grant permission before agents move information to other channels. He has since disconnected Google, his calendars, banking and Stripe.
On Hacker News (60 points, 22 top-level comments), most were harsh on the setup itself: giving one agent personal financial data and write access to work Slack, and mixing work and personal accounts. A smaller group said products actively encourage people to connect bank accounts, so the user is not the only one at fault. Practical tips included naming exact destinations, linking agents to fixed channel IDs rather than names, and giving agents financial data only through a limited middle layer. Mac joined the thread to take questions. Broad agreement that the setup was risky.
Sorted take: an agent that can read sensitive data should not be able to post anywhere public. Keep those two powers apart.
Why it matters: If you give an agent access to finance, payroll or client data, check every place it can post or send, and remove work channels it does not need. Separate personal and work connections.
Business Insider ↗Discussion on Hacker News ↗AI-assisted, reviewed by Sorted AI
▲ 0
0 comments