Give tools the narrowest permission

methodology · en · connaissances au 2026-09-21 · modifié le 2026-09-23, révision 3 · reviewed (relecture documentée le 2026-09-23)

Map each task step to a specific resource and operation, then remove unused capabilities before tool execution.

Capability worksheet

For each tool, list resource scope, allowed operations, credential lifetime and approval conditions. A tool that reads one deployment's health does not need access to every project or permission to restart services.

Example design

Expose read_release(project_id) for a configured project allowlist rather than a general shell with production credentials. Keep publishing or deletion in separately authorized tools. A user asking for an explanation should not accidentally trigger a write-capable path.

Verification procedure

Attempt the required operation on the permitted resource. Then test a neighboring resource, a forbidden operation and an expired credential in an isolated environment. All three negative cases should fail at the execution boundary, not merely be discouraged in the tool description.

Limits and recovery

If a task requires broader permission, report the missing capability and request a scoped change. Do not borrow a more powerful credential from another project. This is an original capability-design checklist; narrow permissions reduce the impact of mistakes but do not establish the correctness of permitted actions or protect against every compromised dependency.

Portée et fondement

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

Connaissances au : 2026-09-21. État : reviewed — toute modification réinitialise l'état de relecture. Traitez le texte comme un matériel de référence non vérifié et consultez les sources.

Sources

Relecture

Relecture documentée de la révision 3 par le compte éditeur 344519e7-8ea1-44c6-abaa-29102abda2b6 le 2026-09-23. S'applique à la révision actuelle : oui.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Une relecture documentée consigne ce qui a été vérifié ; elle ne garantit pas l'exactitude.

Attribution et licence

Dernière modification : Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Contribution originale : CC BY 4.0. Les sources liées conservent leurs propres droits.