1. What Is AI Context Governance?
9 entriesWhy the information an AI model or agent receives needs ownership, quality, access control and audit. Context is the new attack surface and the new source of truth for agents.
2. Context Risks: Injection, Poisoning and Leakage
12 entriesThreats that arrive through retrieved documents, tool output and memory. Treat all retrieved content as untrusted input.
3. Access Control and Policy for Context
11 entriesMake sure an agent only retrieves what the user is allowed to see. Enforce permissions at retrieval time, not just at the model.
4. Privacy, PII and Data Protection in Context
12 entriesDetect and remove sensitive data before it enters prompts, memory or logs. Redact first, retain least, and keep consent and purpose attached.
5. Provenance, Lineage and Metadata for Context
14 entriesKnow where every piece of context came from and whether it can be trusted. Provenance lets you trace an answer back to its sources.
6. Governing Agent Memory and Retrieval Stores
12 entriesPolicies for what agents remember, retrieve, update and forget. Memory needs retention, deletion and review like any other data store.
7. Observability, Audit and Evaluation of Context
13 entriesTrace what context an agent used and test that governance works. If you cannot trace the context, you cannot defend the answer.
Frequently Asked Questions
What is AI context governance?
AI context governance is the set of policies and controls over the information an AI model or agent receives and remembers: its sources, quality, ownership, permissions, privacy treatment, provenance and retention. It makes sure agents use trusted, authorised context and that each answer can be traced and audited.
How is context governance different from data governance and AI governance?
Data governance manages data assets, and AI governance manages models, risk and use cases. Context governance sits between them and acts at run time: what a specific agent may retrieve for a specific user and task, and what ends up in prompts, tool output and memory.
What risks does ungoverned context create?
Prompt injection through retrieved documents or tool output, poisoned knowledge bases, leakage of private or regulated data, users seeing documents they should not, stale or conflicting facts, and no way to trace an answer back to its sources.
How do you enforce access control on retrieved context?
Carry the user's identity through the agent, filter retrieval by permissions at query time using a policy engine or relationship-based authorisation, partition vector stores by tenant, and use delegated credentials rather than shared service accounts. Do not rely on the model to withhold data it has been given.
How do you defend against prompt injection in context?
Treat retrieved and tool content as untrusted data, separate instructions from data, limit what tools an agent can call after reading untrusted content, require approval for sensitive actions, scan inputs and outputs, and test with red-team tools. Design patterns such as CaMeL and the lethal trifecta guidance help.
What should be governed in agent memory?
Decide what may be stored, for how long, who can read or edit it, how users can view and delete it, and how facts are corrected. Record provenance for each memory and apply the same privacy and retention rules as other personal data.
What is an AI context platform?
An AI context platform assembles trusted business context for agents from metadata, semantic layers, knowledge graphs and policies. Gartner has published a market overview of these platforms, and this site lists vendors on its Enterprise AI Context Platforms page.
How current is this list?
Links were checked in November 2026. A few sites, such as Gartner, ISO, BigID, DataHub and Arize, block automated checks and may need a manual click. This page is a resource list, not legal or security advice, and tool descriptions reflect each project's own positioning.