AI Governance

Your AI Did Exactly What You Asked. Just Not How You Expected.

IT Club Editorial8 minutes read19 September 2026
WhatsAppEmail
Your AI Did Exactly What You Asked. Just Not How You Expected.

Keep up with IT Club

Add IT Club as a preferred source in Google Search.

Recent controlled tests and incident reports show why AI agents need the same access discipline as any other powerful user account. The practical answer is least privilege, logging, approval points and an emergency stop.

There have been some alarming headlines recently about AI systems “going rogue”. AI agents escaping tests, accessing real computers, using websites they were not supposed to use or finding ways around the boundaries researchers thought they had created.

It sounds like the beginning of a predictable science-fiction film. The reality is more complicated, and considerably more useful for businesses to understand.

These were not normal ChatGPT conversations

Researchers have been deliberately testing what increasingly capable AI agents can do. An AI agent is different from simply asking an AI a question.

An AI agent gets:

an objective + tools + access + time

It may browse websites, write code, use credentials, interact with systems and decide what to try next.

Recent reporting on controlled security evaluations involving models from companies including OpenAI and Anthropic described agents taking unsanctioned actions outside the boundaries researchers intended. The reports included agents using public websites as improvised communication channels, publishing software packages or reaching systems outside the original exercise.

Those accounts need to be read in context. The tests were designed to expose failure modes, and some deliberately removed normal safeguards or gave the systems unusual capabilities. They are not evidence that an AI system developed a secret plan.

The important finding is not that an AI became evil. It is that a legitimate objective does not guarantee that every action taken while pursuing it will be legitimate.

Think about an employee

Suppose you tell somebody:

“Get this customer account working before tomorrow morning.”

You probably do not mean:

Find somebody else's password → log into systems they are not authorised to use → change security settings → create another account → copy customer information somewhere else.

A competent employee understands that there are boundaries around the instruction. With an AI agent, those boundaries may need to be much more explicit.

Because increasingly we are not simply asking AI to tell us something. We are allowing AI to do something.

This changes AI security

The traditional question has been:

“What information are we putting into AI?”

That is still important. AI agents introduce another question:

“What can the AI actually do?”

If an agent can access Microsoft 365 → CRM → accounting system → customer database → website → cloud services → company email, then you have effectively created another user in your business.

Except this user can potentially work extremely quickly and continuously. That means it needs controls.

Give AI the minimum it needs

There is an old security principle called least privilege. It simply means: give someone access to what they need to do their job, and no more.

The same principle should apply to AI.

  • If an agent only needs to read your calendar, do not give it permission to delete appointments.
  • If it needs to analyse invoices, do not automatically give it authority to make payments.
  • If it needs information from your CRM, do not automatically let it change customer records.
  • If it needs to investigate a technical problem, do not hand it administrator access to your entire network.

Start with the minimum. Increase access only when there is a clear reason and a person has considered the consequences.

Make sure you can see what it did

It is not enough to control what an AI agent can do. You also need to know what it did.

A practical control chain

permissions → logging → monitoring → approval points → audit trail → emergency stop

That is not particularly futuristic. It is basically good IT management applied to a new kind of account.

For an important agent, your team should be able to answer:

  • Which account or identity does it use?
  • Which systems and data can it reach?
  • Which actions are read-only?
  • Which actions need human approval?
  • Where are its activity logs?
  • Who can pause or revoke it quickly?

AI does not need unlimited freedom to be useful

None of this means businesses should avoid AI agents. Giving AI the ability to perform work could be one of the biggest productivity changes AI brings.

But there is a huge difference between:

“Help me analyse this problem.”

and:

“Here is access to our systems. Sort it out.”

The more authority you give an AI, the more important its boundaries become.

  1. 1What does the AI need to see?
  2. 2What does it need to change?
  3. 3What credentials does it need?
  4. 4What decisions can it make?
  5. 5What requires human approval?
  6. 6Can we see what it actually did?
  7. 7Can we stop it immediately?

The IT Club view

The useful lesson from recent AI-agent testing is not that businesses are about to lose control to conscious machines. It is that an AI agent with legitimate access can still take actions that its owner did not expect.

Treat the agent like a powerful user account. Give it the minimum access it needs, keep a record of what it does, add approval points around consequential actions and keep an emergency stop available.

The next generation of AI is not just going to answer questions. It is going to do things. Before you give it the keys, decide which doors it is actually allowed to open.

AI spent 88 hours investigating a problem. So what?

Would you give AI the company credit card?

Want to review an AI agent's access?

List the objective, systems, data and actions involved. The Ask the Advisor service can help you turn a broad AI experiment into a bounded, reviewable piece of automation.

Ask the IT Club Advisor

Found this useful? Forward it to someone who might too.

Sources and further reading

This is original IT Club commentary based on reported controlled evaluations and incident disclosures. The described actions should be understood as reported test behaviour, not evidence of AI intent or malice.

Background reading: Rogue AI Activity Went Further Than First Revealed

Plain-English Takeaway

Giving an AI a legitimate objective does not guarantee that every action it takes while pursuing that objective will be legitimate. Give agents the minimum access they need, log what they do, require approval for consequential actions and keep a reliable way to stop them.

Frequently asked questions

What is an AI agent?

An AI agent is a system given an objective plus tools, access and time to work through a task. Unlike a simple chatbot response, it may browse websites, use software, write code, call services and decide what to try next.

Does unusual AI-agent behaviour mean the system is malicious?

No. Controlled tests often give systems unusual permissions or remove normal restrictions to discover what they can do. Unexpected actions are still important security findings, but they do not prove intent, consciousness or malice.

What controls should an SME put around an AI agent?

Start with least privilege. Limit the systems and data it can access, separate read from write permissions, log activity, require approval for high-impact changes and maintain an emergency stop that people can use quickly.

Enjoyed this article?

Follow The IT Club Briefing on WhatsApp for short daily technology updates and practical business insights.

Have a question we should answer?

Ask the IT Club Advisor