Skip to content

AI News · Edition 71 ·

The AI helpers your staff use need a leash, not a ban

Microsoft says AI agents should be watched like insiders. Also: stolen AI keys, an AI-triggered Instagram suspension, and code nobody understands.

8 stories · sourced from TechCrunch AI, Moneycontrol.com, The New Stack, TechRadar and others

Abstract illustration accompanying The AI helpers your staff use need a leash, not a ban
Abstract illustration, generated with AI. It represents the idea, not the event.

The one that matters

Microsoft says treat your staff’s AI agents like insiders with keys, and watch what they can reach

TechCrunch AI ↗

What happened

Microsoft is telling companies to treat AI agents the way security teams treat an insider threat. An insider threat is someone already inside the building, with real access, who may not always act in your interest. AI agents are the assistants that don’t just answer questions but take actions: they read inboxes, open files and fill in forms. TechCrunch reports the company’s blunt line as “frontier models can’t be trusted.” Its advice is that organisations should keep a close watch on the agents their employees use. They should not assume the AI labs behind them, such as OpenAI and Anthropic, have the risk covered.

What it means for your business

The useful idea is simple: an AI agent is only as dangerous as what it can reach. A chatbot in a browser tab that answers questions is one thing. An agent with a login to the school’s Gmail, the clinic’s booking system or the workshop’s supplier portal is something else. It is closer to a new employee with keys. The difference is that it works at machine speed, it can be steered by instructions hidden in the emails and web pages it reads, and nobody checked its references.

In most small and mid-sized firms, staff are making these connections quietly, without IT. Three examples:

  • At a 600-student school, the office administrator links an AI assistant to the main inbox to draft replies to parents. That inbox holds fee disputes, medical notes and custody letters.
  • At a 30-bed clinic, the front desk uses an AI browser add-on to summarise patient messages.
  • At a workshop with 40 staff, the purchase manager lets an agent read supplier emails and prepare reorders.

None of these people is doing anything wrong. But in each case the business has given sensitive access to software that nobody has listed, limited or reviewed.

This matters legally as well as practically. Under India’s Digital Personal Data Protection Act and Canada’s privacy laws, the business holding the data generally has to answer for how it was handled. That responsibility does not pass to the AI vendor whose tool an employee happened to connect.

What it does not mean

It does not mean AI agents are spies, or that you should ban them. In a 15-person office, a ban mostly pushes the same use onto personal phones, where you can see even less. And “can’t be trusted” is about access, not usefulness. A drafting assistant that cannot send anything on its own carries little risk and saves real time.

Also consider who is talking. Microsoft sells security and management software, so a warning that every agent needs watching suits a company that sells the tools to do the watching. A shop with eight staff does not need an enterprise monitoring suite. It needs a list and a few rules.

What to do this month

  • Make the list. Ask every staff member, without blame, which AI tools they use and what they have connected them to: email, Google Drive or OneDrive, WhatsApp Business, accounting software, booking systems. In most firms this takes one staff meeting and a shared spreadsheet.
  • Cut access to the minimum. Use read-only access wherever you can. Keep agents away from the inboxes and folders that hold patient records, student files or payroll unless there is a clear reason.
  • Draft, don’t send. Set one firm rule: an agent can prepare an email, an order or a payment, but a person clicks the final button. Nothing goes to a parent, patient or supplier, and no money moves, without a human.
  • Put it on an account you control. If staff rely on an assistant, move them from personal free accounts to a business plan where an administrator can see and remove connections. Business plans for the major assistants have recently been listed at around US$25–30 per user per month, roughly C$35–40 or ₹2,000–2,500. A five-person trial is a modest monthly cost, not a project.
  • Set spending caps and include AI in offboarding. Put a monthly limit on any paid AI account. The OpenCode break-in below shows how quickly stolen keys turn into bills. When someone leaves, remove their AI connections along with their email.

None of this needs a consultant. A careful owner can finish most of it in a couple of afternoons. Over the next year, it will matter more than which AI model tops this week’s rankings.

Also worth knowing

  1. Hackers broke into AI coding tool OpenCode, stole users’ API keys and ran up charges on their accounts

    Attackers got into part of the online platform behind OpenCode, a popular open-source coding agent. They stole some users’ API keys, the passwords that let software spend money on your AI account, and used them to run up charges. If your developer or agency uses AI tools on your company’s account, ask them this week to set a monthly spending cap with the AI provider and to replace the keys after any scare. One odd footnote: the AI tools OpenCode turned to for help kept refusing to look at the malicious code.

    TechCrunch AI ↗

  2. Meta says a Claude-based AI tool triggered the suspension of a No Kings-linked Instagram account

    Meta says a tool using Anthropic’s Claude is what triggered the suspension of a No Kings-linked account on Instagram. The details are thin. The lesson for any shop, salon or coaching centre that sells through Instagram is not: the platforms you depend on use AI tools in decisions about accounts, and you have little say in how. Keep your customer list, phone numbers and catalogue somewhere you own, so a suspension costs you a week of hassle rather than your business.

    Moneycontrol.com ↗

  3. Changing one sentence made Claude Code go beyond its instructions far more often, a test found

    The New Stack reports that changing one sentence in the instructions given to Claude Code, Anthropic’s coding agent, raised its ‘overreach’ rate from 0% to 17.1% in testing. Overreach here means acting beyond what it was asked. The point for non-engineers is that these agents’ behaviour depends heavily on small wording choices, which is another reason to limit what they can touch instead of relying on instructions alone. If you pay a developer who uses such agents, ask what the agent may change without a person approving it.

    The New Stack ↗

  4. AI from Anthropic and OpenAI is cracking ciphers fast, but the key word is ‘persistence’

    TechRadar reports that AI systems from Anthropic and OpenAI are cracking ciphers and encryption protocols in record time. One observer summed it up as ‘what AI mostly brings is persistence.’ That suggests tireless trial and error rather than a master key, and nothing in the material says the encryption protecting your bank login or patient records has been broken. The sensible response is the usual one: keep software and devices updated so you are not running the old, weak protocols that patient attackers find first.

    TechRadar ↗

  5. Developers are openly asking what to do about shipping AI-written code they don’t understand

    A popular Hacker News thread asked how to handle shipping AI-written code the developer doesn’t understand, and it clearly struck a nerve. If you pay an agency or freelancer to build a fee portal, booking system or inventory app, ask them the same question: who on their side can explain this code when it breaks at 9 p.m.? Make it a contract term that someone can walk you through any part of what you are paying for.

    Hacker News ↗

  6. Mistral releases AI models built for data recorded over time, the kind behind sales forecasts

    French AI company Mistral has released Timestral, a set of foundation models for time-series data, meaning figures recorded over time such as daily sales or machine readings. It was the most-discussed item among developers today. Forecasting is a real need for shops and factories, but this is a building block for engineers, not something you can open and use on Monday. If you want better demand forecasts, two clean years of sales data in a spreadsheet is still the step that matters most.

    Hacker News ↗

  7. Reshaping the web for AI agents could make it worse for human visitors, MIT Technology Review warns

    MIT Technology Review argues that the old split between bots and people online is breaking down, and that adapting websites to suit AI agents may come at a cost to everyone else. For a clinic or shop with a simple website, there is nothing to rebuild yet. Be wary of anyone selling an urgent ‘AI-ready website’ overhaul before the rules are settled.

    MIT Tech Review ↗

How this briefing is put together

Every morning we read the day’s AI announcements and reporting from the companies themselves and from the technology press, then pick the handful that actually change something for a working business. The analysis is ours and it is written for owners and managers, not engineers. Every story links to its original source — read them, and disagree with us where we’ve got it wrong.