permission-attenuation

Least-privilege enforcement validates each agentic sub-task receives only the minimum permissions strictly required, preventing privilege creep and credential exposure across task boundaries. Scoped credentials are used instead of raw or broad credentials. Permissions are revoked immediately after the sub-task completes.

Sub-processes inherit parent permissions without scoped credential handling, allowing privilege creep. This skill stops tools from inheriting parent permissions by enforcing tight, time-bound access for each specific sub-task and flagging permissions for revocation upon completion.

Preventing raw credential flow requires scoped credential handling that restricts broad credentials from passing to sub-tasks. This skill validates that only the minimum necessary permissions are granted per sub-task and ensures revocation after use to avoid persistent access.

Minimum-privilege enforcement is designed for agentic workflows that chain tools, APIs, or external services. It ensures each tool in the chain receives only the permissions it strictly requires and enforces per-task revocation to prevent persistent access after completion.

Least-privilege checks are needed whenever Claude orchestrates tools, APIs, or external services and delegates tasks. They prevent privilege creep by validating scoped credentials per sub-task and requiring revocation after use to eliminate persistent access vulnerabilities.

Permission attenuation requires no external dependencies. You install the SKILL.md file into your Claude skills directory and activate it before orchestrating any tool calls to enforce least-privilege access and per-task revocation.