How would you raise concerns about an AI tool connected to directory services?

Frame it as a change-control and access-scope issue, not an argument about AI in general. Ask who approved the connection, what permissions the account has, which environment it can reach, and how its activity is logged. If those answers are unclear, recommend pausing write access while the integration is reviewed.

Bring a concrete next step: document the service account’s permissions, verify the change and recovery procedures, and test the intended workflow in an isolated non-production environment. That gives management a way to assess the value without treating production as the test bed.

First establish what “connected” actually means. Read-only directory lookup is a different risk from permission to modify groups or user attributes. Get the account’s effective permissions and credentials reviewed by whoever owns identity security, then reduce access to the minimum needed for a defined task.

If changes are genuinely required, consider requiring human approval for each change and keep the AI away from direct production writes until the workflow has been tested. Also check whether the account is monitored and whether its credentials can be rotated or disabled quickly.

I’d keep the message short and operational: “This integration may have write access to production identity data, and we don’t yet have a documented approval, permission review, or recovery plan. Can we temporarily limit it to read-only or a test environment while those are checked?”

That is not being anti-technology. It makes the risk and the requested decision clear, without predicting a disaster or making it personal.

Don’t assume the AI itself will make mistakes in a particular way. The basic concern is that any service account with broad write permissions can cause damage, whether its actions come from an AI workflow, a script, or a person. Focus on limiting those permissions and making changes auditable and reversible.

If there’s no change approval or security review for this connection, escalate that process gap through the appropriate internal channel. Keep a factual record of what you observed and what you asked to have reviewed.