Scope access to the requested work
Prefer a specific project folder, read-only access, or a limited tool credential when sufficient. Avoid granting broad account or organization access just to simplify one task.
Identify secrets, personal data, production records, and generated files that should remain out of scope. If the task depends on them, define exact fields or actions and use an approved path that avoids copying sensitive values into prompts or logs.
Review access and outputs
Check each connected tool's permission model and whether it inherits access from the signed-in user. Remove temporary grants after the task and rotate credentials if they were exposed or copied to an unsafe location.
Inspect changed files and outputs for accidental disclosure, including logs, screenshots, and reports. Access controls reduce exposure, but they do not replace checking what was actually read or written.