Skip to content
TKOResearch

AI agent readiness questionnaire

Check the controls your agent needs before production access.

Answer 12 practical questions about authority, credentials, data, approvals, injection resilience, logging, and recovery. You will see a review priority, three areas to check, and a suggested 30-day sequence based on your answers.

12-question planning checklist

Review the controls your agent needs before launch.

Your answers stay in this browser. The checklist suggests controls to review and a 30-day planning outline. It does not inspect your system or verify that a control works.

0/12 answered

1. Is the agent's system boundary documented?

Include the model, orchestrator, memory, retrieval, tools, data stores, identities, and operators.

2. What is the agent allowed to do?

Consider read, draft, write, send, delete, approve, deploy, and execute actions.

3. Are credentials scoped to the task and environment?

Look for short-lived tokens, user binding, target restrictions, and separate production credentials.

4. Are high-impact actions approved by a person?

Approval should cover the exact action, target, recipient or deployment being proposed.

5. Have you tested prompt injection and indirect instructions?

Include instructions from documents, webpages, emails, tool output, tickets, and retrieved content.

6. Does retrieved content stay inside the user's authorization boundary?

Ask whether a user can retrieve material they could not open directly in the source system.

7. Are model-generated actions validated outside the model?

Schemas, policy checks, allowlists, target checks, and server-side authorization should enforce the result.

8. Can you reconstruct what the agent did?

Logs should connect the request, action, approval, result and error state. Record only the input and argument fields needed for review, with sensitive values redacted.

9. Can operators contain or reverse an unintended action?

Consider kill switches, rollback, credential revocation, queue cancellation, and recovery drills.

10. Do changes trigger review or reassessment?

Include model swaps, prompt changes, new tools, new data sources, policy changes, and permission changes.

11. Is tenant or customer data isolation verified?

This matters whenever the agent can access more than one customer, role, workspace, or data class.

12. Will operators know when the agent behaves outside its expected path?

Consider alerts for unusual tools, destinations, volume, privilege, errors, and repeated policy failures.

Answer all 12 questions to generate your planning summary. The score is a checklist priority, not a measured risk level or deployment approval.

This assessment is an early planning aid. It is not a certification, penetration test, legal opinion, or substitute for reviewing the actual system boundary, implementation, and operating controls.