Lore
Scoped & Restricted Agent Permission Modes
Overview
When configuring an autonomous agent's access to data and mutating actions, restrict by default and grant narrowly:
- Read-only on shared resources: an agent should default to view-only access on any shared/company-wide database or system it merely needs context from.
- Write access scoped to the owned artifact: grant edit/write permission only to the specific page, database, or file the agent is responsible for producing or maintaining — never to the broader shared resource it reads from.
- Named restricted modes: define an explicit, named mode that allow-lists only non-mutating tools (read + answer, no writes) for contexts requiring guaranteed non-destructive behavior. Notion AI's "Ask mode" is one such spec — it bans all mutating tools and permits only reading and responding.
Named modes like Ask mode are typically captured as their own entry in a Specification-Driven Development spec library, so the permission boundary is documented and versioned rather than implicit in code.
Example: Notion's meetings-database agent
An agent tasked with maintaining a meetings database is given view-only access to the rest of Notion's shared workspace (so it can read context) but edit access only to the meetings database itself — preventing it from ever mutating unrelated company data.