# Scan Roles Scan roles enable role-based probing of agentic systems to validate access controls, tool permissions, and authorization boundaries. By defining scan roles, you can ensure agents enforce correct access controls and prevent unauthorized tool execution or data access. You can create custom scan roles representing different personas or scenarios, ensuring each role can only perform authorized actions within your agentic system. ## Common Scan Roles **TEST\_USER**: Standard user role for probing typical agent interactions and permissions. **ATTACKER\_TOKEN\_ALL**: Simulates an attacker with compromised credentials to validate security boundaries. **MEMBER**: Regular member role for probing team-level access controls and collaboration features. For information on creating scan roles, refer to [Create a Scan Role](/akto-argus-agentic-ai-security-for-homegrown-ai/agentic-red-teaming/how-to/create-a-test-role.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ai-security-docs.akto.io/akto-argus-agentic-ai-security-for-homegrown-ai/agentic-red-teaming/concepts/test-role.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.