Default deny
The rule that an agent action requiring a checkpoint does not proceed if the approval infrastructure fails, the approver is unreachable, or no approval policy yet exists for the action, per the framework's own recommendation (MGF v1.5, p.29). The opposite, proceeding on a timeout, converts a checkpoint into a delay rather than a gate.
Defined in 2 GAGE programs, which carry 2 distinct definitions of it. The wording above is taught in Certified Agentic AI Governance Professional (CAAGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The rule that an agent action requiring a checkpoint does not proceed if the approval infrastructure fails, the approver is unreachable, or no approval policy yet exists for the action, per the framework's own recommendation (MGF v1.5, p.29). The opposite, proceeding on a timeout, converts a checkpoint into a delay rather than a gate.
The stance that an agent holds no capability it has not been deliberately granted, so the question for every tool is "is there a reason to grant this," not "is there a reason to withhold it." The opposite, default allow, is granting broad access and restricting later, which is how agents become over-privileged.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Checkpoint Design · Meaningful Human Accountability, Certified Agentic AI Governance Professional (CAAGP)
- Permissioning an agent: tools, budgets, and the actions it may never take alone · Agents Under Command, Certified AI Governance Professional (CAIGP)
Where it shows up at work
A definition is where Default deny starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Designs multi step agent systems: orchestration graphs, tool contracts, memory, interruptibility, and the evaluation of agent behavior before it is allowed to act.
2 lessons on this page teach it as a primary outcome.
Governs AI agents that take actions: tool access, least privilege, interruptibility, cascading actions and accountability for what an agent did.
One lesson on this page teach it as a primary outcome.
Defines who reviews AI outputs, what they check, when they can override, and how to keep review from becoming a rubber stamp.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- Agentic AI Engineer, orchestration editionneeds it at depth
- Chief Information Security Officer, AI security focusneeds it at depth
- VP of AI Governance and Ethicsneeds working knowledge
- AI Security Architectneeds it at depth · 8 open postings this week
- Chief Technology Officer, AI engineering editionneeds working knowledge
- AI Governance Engineerneeds working knowledge · 7 open postings this week
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: IMDA Model AI Governance Framework for Agentic AI; NIST AI RMF; EU AI Act Article 14; ISO/IEC 42001 Annex A.
One interview question about it
An agent you built can call five tools. How do you keep a bad plan from becoming a bad action, and how do you test that before launch?
Asked of candidates for agentic systems engineering. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.