Read the permissions. Keep the control.

A useful connection should get the access it needs for the task—and no more.

Start with scope

Where supported, limit access to a project, repository or workspace area. Use a test account for evaluation. Keep production credentials out of copied prompts, shared links and screenshots.

Separate reading from acting

Reading a document is different from sending an email, changing a customer record or publishing code. Ask your client to stop for approval before consequential writes. A tool description alone is not a guarantee of behavior.

Treat retrieved content as data

Documents and tool responses can contain instructions from someone else. Do not let those instructions expand the original task or authorize access to unrelated systems. Check suspicious requests with the person responsible for the task.

Have an exit plan

Know how to revoke access, rotate a credential and remove the connection. Record who owns the integration and when it should be reviewed. If credentials leak, removing a public copy is not enough; revoke or rotate them.

Keep exploring

Updated October 7, 2026. Provider documentation can change.