An agent often begins with one narrow job and gradually acquires more tools, scopes, exceptions, and shared credentials. Without a deliberate review, the system's effective permission can become much broader than anyone intended.
Freeze capability meaning
Do not let a tool slug change behavior in place. Pakkawork content-addresses every contract and keeps old versions resolvable. New parameters, scopes, methods, or paths require a new version and hash.
Bind permissions to purpose
- Register the agent's owner, model, purpose, and risk ceiling.
- Grant only the apps and OAuth scopes needed for that purpose.
- Use personal connections unless team sharing is intentional.
- Block actions outside the expected contract patterns.
- Suspend first and review when behavior drifts.
Review the effective surface
A useful review compares contracts, connection scopes, tenant rules, system-floor rules, and recent actions. Looking at any one layer alone can hide an accidental capability created by their combination.
Treat exceptions as product decisions
Temporary policy exceptions should be narrow, attributable, and expiring. Repeated exceptions indicate that the workflow or contract catalogue needs redesign—not that the control plane should become permanently permissive.
Frequently asked
Does adding a tool automatically authorize an agent to use it?
No. Catalogue availability, OAuth scopes, agent identity, and policy are separate gates.
How can a team detect permission creep?
Compare the agent's registered purpose with its recent contract usage, connection scopes, policy exceptions, denials, and approvals.