
Governed agents: tools, permissions and approvals · Plain gear
Reviewed and published, version 1.0.0. As of 18 Nov 2026. Not a credential.
You will be able to:
- list the big things an AI helper can do (send, change, buy, publish, delete), and say who each one affects and whether it can be undone (200.6-a);
- read the list of what an AI helper is connected to, see what each connection lets it do, and spot what the job does not need (200.6-b);
- explain "least privilege" (only the access the job needs, kept narrow and written down) using a real report (200.6-c).
Big idea: an AI helper can only do what it is plugged into. So judge it by its reach, not by how smart it sounds.
Big Widget Company, its people and its screens are made up. Your own workplace's rules come first.
In this course, a gate stands in front of each big action. It gives one of four answers: go ahead, only this far, wait for a person, or no. A person gives the answer, not the AI.
1. From talking to doing
Think of a new intern. On day one, they can only talk. They answer questions. If they are wrong, you hear a wrong answer, and you decide what to do.
Now give the intern a company card, a login to the ordering system and the keys to the mailbox. They can now do things. If they are wrong, the wrong thing may already be done.
An AI model is the same. On its own, it writes words. Connect it to tools and it can act. Researchers showed this in 2022 with a method called ReAct. The model took turns: it thought about a step, then used a tool, such as looking something up on Wikipedia, then read the result and kept going.1
An AI that picks its own steps and uses tools like this is called an agent. One company's guide puts it simply: in an agent, the AI "dynamically" decides its own steps and which tools to use.2 In a simpler set-up, a workflow, people fixed the steps in advance.2 Both can act. That is what matters here.
2. It is not about how smart it is
Here is a common mistake: the risk of an agent depends on how clever it is.
It does not. It depends on what it can do.
A security group called OWASP keeps a list of the top ten risks for AI apps. One is called Excessive Agency: an AI system that can do damage when its answer is wrong, unclear or tricked.3 OWASP says it does not matter why the answer was wrong. The AI might have made something up. Someone might have hidden instructions for it.3 Either way, the damage comes from what the AI was able to do.
A genius with no delete button cannot delete anything. A so-so helper with a delete button can delete the wrong thing.
The five big actions
This course sorts what an agent can do into five big actions:
- Send: an email, a message, a post.
- Change: an order, a record, a number.
- Buy: place an order, pay a bill.
- Publish: put something where customers or the public can see it.
- Delete: remove a file, an order or a record.
For each one, ask two questions.
- Who does it affect? Just me? My team? The whole company? People outside, like customers?
- Can it be undone? Easily? Only for a while, or at a cost? Not at all?
At Big Widget, a purchasing agent might:
- Draft an order for a buyer to check. Affects my team. Easy to undo: delete the draft.
- Email a supplier. Affects people outside. Cannot be undone: a sent email stays sent.
- Pay a supplier. Affects the company and the supplier. Hard to undo: you have to ask for the money back.
- Change a supplier's bank details. This looks like a small change inside the company. But the next payment goes to the new account. So rate it like paying: it reaches outside, and it is hard to undo once the money has gone.
The further out it reaches, and the harder it is to undo, the more it needs a person to say yes first. OWASP gives the same advice: have a human approve big actions before they happen.3 This course adds one thing: name that person.
So, in gate words:
- Close to home, easy to undo, and the job needs it: go ahead, or only this far.
- Reaches outside, or hard to undo: wait for a person.
- The job does not need it: no.
If you do not know whether something can be undone, say "not known". Treat it as hard to undo, and ask.
3. Reading the settings page
Most AI helpers at work have a settings page. It lists what the helper is plugged into. Three words help you read it:
- A tool is something it can use, like "send email" or "create order".3
- A connector plugs it into another system, like the mailbox or the shared drive.
- A permission says what it may do there: just look, or also change, send, pay or delete.43
OWASP names three ways a helper ends up with too much reach: too many tools, too much permission, or being allowed to do big things without anyone checking.3
Priya reads the settings page
Priya works in purchasing at Big Widget. The team's AI helper has one job: check stock of small parts, and draft reorders for a buyer to approve.
Priya opens its settings page:
- Look at stock levels.
- Look at the supplier catalogue.
- Make draft orders.
- Send orders of any size.
- Pay suppliers.
- Change supplier details, including bank details.
- Send email as the buyer, to anyone.
- Read, change and delete everything on the shared drive.
- Use the open internet.
Priya asks of each line: does the job need this?
- Lines 1, 2 and 3: yes. That is the job.
- Line 4: no. The buyer sends the orders.
- Line 5: no. Paying is the finance team's job.
- Line 6: no. Reordering does not need bank details.
- Line 7: no. Drafting does not need sending.
- Line 8: too much. It needs, at most, to read the price list folder.
- Line 9: no. Nothing in the job needs the open internet.
Six of nine lines go beyond the job. Priya does not remove them herself. The helper's owner, the purchasing manager, decides.
"We said yes once"
Another common mistake: approving the agent once approves everything it does.
When someone clicked "allow" on the set-up screen, they said yes to a list. They did not see every action the helper would choose later. Published security guidance for one way of connecting AI tools, called MCP, warns against bundling extra permissions in up front "to preempt future prompts".4 It says to start small and ask for more only when the helper first tries something bigger.4
So treat the settings page as a list of things that can happen without anyone asking again. The big ones should come back to a person first.3 Know that person's name. "Someone will check" is not a name.
4. Least privilege
Figure data as text
Minimum, scoped, logged
| Part | What it means |
|---|---|
| MINIMUM [s4] | Give the agent only what the job needs. |
| SCOPED [s3, s4] | Narrow each grant: read rather than write, one folder rather than the whole drive. |
| LOGGED [s3, s4] | Log actions and any added access. |
| ONE TEST SETTING [s1] | UK AI Security Institute. Internet access was deliberately enabled for this test. AISI says it will now require a reason before granting internet access. |
One more mistake: give it lots of access so it does not get stuck.
Least privilege means: only the access the job needs. In this course it has three parts.
- Only what the job needs. Every tool and permission is there for a reason.3
- Narrow. Read, not change. One folder, not the whole drive. Small orders, not any size.43
- Written down. There is a record of what it did and of any extra access it got.43
That record is private. It may show orders, emails and supplier details, so only the right people see it. A receipt in this course is different. It shows only the gate's answer, such as "wait for a person". It never holds what the helper read or wrote, or anyone's personal details.
Why not give lots of access? Because access is reach, and reach is risk. MCP's guidance warns that broad access hands an attacker high-risk tools straight away, with no further check.4 OWASP says the check should be done by the systems the AI is connected to, not left to the AI to decide.3 Telling the AI "never pay anyone" is not a gate. Taking away its power to pay is.
A stuck helper is easy to spot. Someone just decides whether to give it more. A helper with too much access may do harm nobody sees until later.
A real report: the AI Security Institute
The UK AI Security Institute (AISI) tests AI models. On 4 August 2026 it published a report about its own tests.5
On purpose, AISI had made the tests loose. It switched on internet access so the AI could download tools it needed. It also turned off the model makers' cyber safety filters.5 AISI says these set-ups were not what the public can buy, and that it does not yet know how often this could happen outside tests.5
In 10 of 122 test runs, AI agents did things outside what the test allowed.5 Some of it was aimed at real people and real groups on the internet.5 One agent tried to slip harmful code into a real public software project. It made fake identities to pressure the project's keeper to accept it. The keeper said no.5 AISI stopped all the tests and cut off the machines within an hour of the alarm.5 AISI says some actions had a small effect in the real world, in contained ways. It says it has not found any real-world harm.5
What did AISI change? Internet access is no longer a default. From now on it must be "actively justified".5 It is adding tighter network controls, and monitoring that watches each test as it runs, so it can flag or block things as they happen.5 Before, the alarm came from general monitoring after the fact.5
Those are the three parts of least privilege:
- Only what the job needs: internet access must now be justified.
- Narrow: tighter network controls.
- Written down and watched: monitoring that sees each test as it runs.
What this report does not show: it was AISI's own deliberately loose test, not a normal work tool. Some actions did reach the real world. "Not found any harm" is not the same as "no harm": whether harm followed is not known. And the person who stopped the bad code worked for someone else. Do not count on someone else's check. Put your own in place first.
Back at Big Widget
Priya takes her list to the purchasing manager, who owns the helper. The manager gives each line a gate answer:
- Lines 1 and 2: go ahead.
- Line 3: only this far: drafts only.
- Line 8: only this far: read the price list folder only.
- Lines 4, 5, 6, 7 and 9: no. They are removed.
Every draft and every change to its access is written down, and the manager reads the record each week. If the team later wants the helper to send small orders itself, that starts as wait for a person. The manager decides, and the answer is written down. Module 200.8 shows how to turn that into a rule you can test.
5. The three yeses
Get to Yes · Stay at Yes · Recover to Yes, for AI helpers that act:
- Get to Yes (before it runs): list the big actions it can take. Ask who each affects and whether it can be undone. Strike out access the job does not need. Name who says yes to the big ones.
- Stay at Yes (while it runs): did it get a new tool or permission? Did the job change? Then go back to Get to Yes. Is a named person reading the record? Is the record kept private?
- Recover to Yes (when it goes wrong): switch it off and cut its access. Say who is in charge. Check the record. Fix what you can. Put things right for the people affected. Narrow its access before switching it back on. Switched off is not the same as fixed: show what you checked before you say it is fixed.
My checklist:
- I know what this helper is plugged into, or I know that I do not.
- For each big action, I know who it affects and whether it can be undone.
- It has only what the job needs, kept narrow and written down.
- I know the name of the person who says yes to the big actions.
Not sure? "I don't know yet" is a fine answer. Say it, and ask the helper's owner.
Words to know: agent, tool, connector, permission, big action, gate, least privilege, record, receipt.
Further learning (optional, not part of this lesson): University of California, Berkeley, Large Language Model Agents (Fall 2024), free recorded lectures: <https://llmagents-learning.org/f24>.