Data access
Trace the information available to the application. Check access boundaries, sensitive data handling, and whether one user's information can reach another.
Technology should increase human agency.
Try the free AI independence checkKnow what your AI can access, what it can change, and where the controls need work.
Discuss a reviewBefore an AI application gets more access, examine how it uses the access it already has.
Trace the information available to the application. Check access boundaries, sensitive data handling, and whether one user's information can reach another.
Examine identities, credentials, and the actions an agent can take. Identify where access should be narrower and where authorization needs to happen outside the model.
Test agreed scenarios, including malicious instructions in retrieved content, unexpected tool use, and actions taken with incomplete information.
Check how people review consequential actions, investigate errors, revoke access, and stop or recover a workflow.
We agree on the application, access, test scenarios, and reviewer responsibilities before work begins. Testing stays within the systems you authorize.
Discuss your applicationA record your product and engineering teams can use.
The reviewed data sources, tools, identities, and dependencies, with assumptions and scope recorded.
Evidence from the agreed tests, the conditions that produced each finding, and its practical consequence.
Recommended changes, their dependencies, and what should be addressed before extending access or use.
How the fixes should be checked. Implementation and follow-up testing can be scoped with the review.
For a practical introduction to tool permissions, read our authorization example. It is a teaching example, with its limits documented.
An opportunity assessment can help define the workflow and whether implementation is worth pursuing.
Explore the assessment