# Tool permission review

Use this worksheet before exposing internal systems to AI-callable tools. The review should make tool authority explicit enough that product, engineering, security, operations, and business owners can understand exactly what the system can do.

## Review fields

- Tool name, owning system, business owner, technical owner, and support contact.
- Allowed operations, denied operations, data classes accessed, and side effects created.
- Authentication method, credential scope, rotation owner, and emergency revocation path.
- Approval threshold by action type, confidence score, customer tier, data sensitivity, and reversibility.
- Logging requirements: input summary, output summary, actor, approval evidence, correlation ID, and retention.

## Production rule

No tool should launch with broad credentials, unclear rollback behavior, or untested failure modes. If the tool can change money, access, customer data, legal commitments, or production systems, approval evidence must be mandatory.