Assess agent-security tooling against the permissions and data paths in your architecture. Look for explicit identities, least-privilege scopes, per-tool policy, credential isolation, network controls, and durable audit records. Define which actions require human approval, such as financial transactions, data mutation, privilege changes, or external communications, and make unavailable approval or policy services fail closed. A scanner should cover indirect prompt injection and malicious tool metadata, not only user prompts. Test the complete action path because a safe model response can still trigger an unsafe downstream tool call.
- 01Tool-level authorization
- 02Memory and context controls
- 03Sandbox boundaries
- 04Audit and approval workflows
Record evidence and limitations for each criterion. A catalog listing is a discovery aid, not a security certification.