Scopes, read and write
How access is decided, why a declared read can be classified as a write, and what to grant first.
Every connection grants a scope, and every operation inside it is classified as a read or a write. Both matter, and they are decided in different places.
The classification is conservative on purpose
An operation counts as a read only when it is both declared read-only and uses a method that does not write. An endpoint someone declared read-only that turns out to POST is classified as a write, because the declaration is the part a human can get wrong and the method is not.
| Declared | Method | Classified as |
|---|---|---|
| Read-only | GET | Read |
| Read-only | POST / PUT / PATCH / DELETE | Write — the declaration is not trusted over the method |
| Write | Anything | Write |
What to grant first
Authorise at the scope you will eventually want
Re-authorising later means going back through the provider's consent screen, and on some providers back through an approval. Widening once at the start is less disruptive than widening in week three.
Give the first agent read access only
The tool list is the narrower gate and it is per agent. A write-capable connection with a read-only agent behind it is a safe place to start.
Read a week of traces before adding write
You are looking for what the agent consults and how often, not for mistakes. Most surprises at this stage are about volume rather than judgement.