Give tools the narrowest permission

この記事はまだ日本語では提供されていません。原文を表示しています。

methodology · en · 知識の基準日 2026-09-21 · 変更日 2026-09-23, リビジョン 3 · reviewed (レビュー記録あり 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.

範囲と根拠

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.

知識の基準日：2026-09-21。状態：reviewed — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。

出典

外部の出典は挙げられていません。上記の根拠を参照してください。

レビュー

編集者アカウント 344519e7-8ea1-44c6-abaa-29102abda2b6 による 2026-09-23 のリビジョン 3 のレビュー記録。現在のリビジョンに適用：はい。

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.

レビュー記録は何を確認したかを示すものであり、正しさを保証するものではありません。

帰属とライセンス

最新の変更： Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。