Governance

AI Agent Governance: 12 Terms Explained

· founder of ETCSEC · updated November 17, 2026 · 9 min
Illustration of a robot character working, with no text or labels, used as the article's generated header.
The short answer

A DSI reviewing an AI agent platform hears the same dozen words in every pitch, agent, agent lead, MCP, guardrail, audit log, shadow AI, rarely defined the same way twice. This glossary defines all 12 terms in plain language, each tied to a primary source, including what a platform does not do, such as detecting shadow AI on its own.

Twelve terms, one shared vocabulary

A person evaluating an AI agent platform runs into the same dozen words in every vendor's pitch: agent, agent lead, MCP, guardrail, audit log, shadow AI. Vendors rarely define them the same way, which makes a real comparison between platforms difficult, and makes it easy to assume a term covers more than it actually does.

This glossary defines 12 of those terms in plain language. The protocol-level terms, MCP, MCP server, tool, come from the Model Context Protocol specification itself. The terms specific to how one platform implements governance, agent lead, audit log, organization isolation, come from Atipol's published product reference, so each definition can be checked against its source rather than taken on faith.

The 12 terms fit on a single flow: a person owns an agent lead, which assigns work to agents; agents call tools exposed by MCP servers, within limits set by tool permissions; a guardrail, sometimes a one-time human approval, sits before anything sensitive happens; and an audit log plus traceability keep a record of the whole path, inside a boundary the next sections call organization isolation.

These definitions matter beyond vocabulary. A security review, a procurement questionnaire, or an internal AI policy will ask variations of the same questions: who can an agent act for, what can it call, who approves a sensitive action, and what gets recorded. Having a precise answer for each of the 12 terms below means those questions can be answered directly, against a primary source, rather than reconstructed from a sales conversation.

The same flow, shown as a diagram:

OwnerOne personAgent leadAssigns &reviews ticketsAgentExecutes thetaskMCP serverTools, underpermissionsGuardrailEnforced limitHuman in theloopOne-timeapproval ifsensitiveAudit log &traceabilityRecords thewhole pathOrganizationisolationEncrypts theboundaryOwnerOne personAgent leadAssigns & reviews ticketsAgentExecutes the taskMCP serverTools, under permissionsGuardrailEnforced limitHuman in the loopOne-time approval if sensitiveAudit log & traceabilityRecords the whole pathOrganization isolationEncrypts the boundary

The actors: agent, agent lead, and runner

What is an agent? An agent is a software process that carries out a task on its own, typically by calling tools, rather than a person carrying out each step by hand. An agent still operates inside whatever limits its platform sets: which tools it can call, and who reviews what it delivers.

Agent

An agent is a software process that executes a task on its own, usually by calling tools, instead of a person performing each step by hand.

What is an agent lead? In Atipol's model, an agent lead is the process that acts for exactly one person: it never has more rights than that person, splits a brief into tickets, assigns each ticket to an agent, and reviews and integrates every delivery before anything is considered finished. An agent never reviews its own work; that review is the agent lead's job specifically.

Agent lead

An agent lead acts for one person and never has more rights than that person; it reviews and integrates the work of the agents it assigns.

What is a runner? A runner is the machine or container an agent actually executes in. Atipol's agents run on a Mac, on Windows, on a Linux binary built for a server, or inside a Docker container used as a server runner, always on infrastructure the user already controls rather than a separate hosted fleet.

Runner

A runner is the machine or container, Mac, Windows, a Linux binary, or Docker, where an agent's process actually executes.

What MCP standardizes: servers, tools, and permissions

What is MCP? The Model Context Protocol, MCP, is an open protocol that enables integration between LLM applications and external data sources and tools, as defined by the protocol's own specification. MCP itself is a connection standard: it does not build in guardrails, audit logs, or approval rules; those come from the platform that implements it.

MCP

MCP is an open protocol that lets an LLM application connect, in a standard way, to external tools and data sources.

What is an MCP server, and what is a tool? An MCP server exposes a set of tools, callable functions such as reading a ticket or querying a database, that an agent can invoke through the protocol. Each one of those callable functions is a tool; a single server can expose several of them.

MCP server and tool

An MCP server exposes tools, for example reading a ticket or querying a database, that an agent calls through MCP.

The exchange below is exactly how the specification itself shows a tools/call request; the server answers with a matching JSON-RPC result (server/tools, revision 2025-06-18).

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_weather",
    "arguments": {
      "location": "New York"
    }
  }
}

What are tool permissions? Tool permissions are the rules that decide which tools an agent, or a sub-agent it delegates part of its work to, is allowed to call. This limit is explicit: a sub-agent never has more permissions than the agent delegating to it, so delegation can narrow what is allowed, never widen it.

Tool permissions

Tool permissions decide which tools an agent may call; a sub-agent never gets more permissions than the agent that delegated the work to it.

Keeping a human in control: guardrails and human in the loop

What is a guardrail? A guardrail is a rule built into the system itself that blocks or limits an action before it happens, rather than a recommendation an agent is free to ignore. A guardrail does not depend on the agent choosing to respect it.

Guardrail

A guardrail is an enforced limit on what an agent can do, built into the system rather than left to the agent's judgment.

What does human in the loop mean? It means a specific, sensitive action waits for a person to approve it before it goes ahead. Atipol is explicit about scope here: human approval is given for one specific call, once, rather than as a standing permission an agent could reuse afterward.

Human in the loop

Human in the loop means a sensitive action waits for a person's one-time approval instead of running on the agent's own authority.

Together, a guardrail and human in the loop cover two different failure modes: a guardrail stops an agent from attempting an action at all, while human in the loop lets an agent request to proceed but still requires a person to say yes before anything happens. A platform with only one of the two leaves a gap the other is meant to close.

Knowing what happened: audit log and traceability

What is an audit log? An audit log is the record of who did what: members, roles, security settings, key openings, and marketplace actions, kept separately from the content of the work itself. Atipol's organization audit log never contains ticket content and exports as CSV; a more extended version, with a choice of retention period and export to a SIEM, is planned specifically for the Enterprise plan, not shipped on other plans today.

Audit log

An audit log records who changed what, roles, settings, key openings, without the content of the work itself.

The Enterprise plan description states this directly: it builds on the Business plan, plus a service commitment, with SSO, the customer key, and that extended audit log all listed as planned rather than available now.

What is traceability? Traceability is the ability to follow one piece of work from the brief that created it to the change that was eventually integrated. In Atipol's model, a ticket's six states, draft, transmitted, in progress, review, integration, done, give that trail a fixed, checkable shape rather than leaving it to memory or a chat log.

Traceability

Traceability means a ticket can be followed, state by state, from the original brief to the integrated change.

Keeping teams apart: organization isolation and shadow AI

What is organization isolation? It means one organization's data is cryptographically separated from every other organization's, rather than pooled in one shared store. Atipol encrypts each organization's data separately, under a hardware master key, and the server opens it for a person only after checking that person's rights.

Organization isolation

Organization isolation means project data is encrypted per organization, with its own key chain, rather than pooled across customers.

What is shadow AI? The term names agents or MCP servers that people inside an organization run outside the platform the organization has actually sanctioned, invisible to whatever governance controls that platform provides. The name describes a risk, not a feature every platform necessarily ships.

A common confusion: naming shadow AI versus detecting it

Shadow AI names a risk, agents or MCP servers running outside a sanctioned platform, not a feature every platform has. Atipol does not, on its own, detect agents or MCP servers installed outside the platform; a glossary entry for the term is not a promise that it gets monitored.

Assistant, agent, or automated workflow?

These three get used interchangeably, but they differ in one practical way: who, or what, decides the next step, and that difference is exactly what decides how much governance each one needs around it.

TermDecides the next stepTypical governance need
AI assistantA person, for each requestNone beyond normal account access
AI agentThe agent itself, within its tools and permissionsGuardrails, tool permissions, human in the loop for sensitive actions
Automated workflowA fixed, predefined sequence, no runtime choiceChange control on the workflow definition itself

An agent lead sits above this table rather than inside it: it is the process that assigns a ticket to an agent in the first place and reviews what comes back, whether that agent behaves closer to an assistant on a narrow task or a fully autonomous actor on a broader one.

The 12 terms at a glance

TermOne-sentence definition
AgentA process that executes a task on its own, usually by calling tools.
Agent leadActs for one person, assigns tickets, reviews every delivery.
RunnerThe machine or container where an agent executes: Mac, Windows, Linux binary, or Docker.
MCPAn open protocol connecting LLM applications to external tools and data.
MCP server and toolA server exposing callable tools, such as reading a ticket, that an agent can call.
Tool permissionsRules on which tools an agent or sub-agent may call.
GuardrailAn enforced limit on an agent's actions, not a suggestion.
Human in the loopA sensitive action waiting for one-time human approval.
Audit logA record of who did what, without the content of the work.
TraceabilityFollowing a ticket from brief to integrated change, state by state.
Organization isolationProject data encrypted per organization, with its own key chain.
Shadow AIAgents or MCP servers run outside a sanctioned platform, invisible to its controls.

A platform that defines these 12 terms this precisely, and is specific about which of them it actually enforces today rather than plans to add later, such as an extended audit log or the exact encryption chain behind organization isolation, is easier to evaluate on its own merits than one that uses the same 12 words as marketing shorthand. That same precision also makes it possible to compare two platforms on exactly these 12 points, rather than on whichever subset each vendor chooses to highlight.

Frequently asked questions

Is an AI agent the same thing as an AI assistant?

No. An assistant waits for a person to decide each next step; an agent decides its own next step within its tools and permissions, which is why guardrails and human-in-the-loop approval matter more for agents than for assistants.

Does MCP itself enforce governance like guardrails or audit logs?

No. MCP is a protocol for connecting an LLM application to tools and data; guardrails, audit logs, and approval rules are built by the platform that uses MCP, not by the protocol itself.

Can a platform detect shadow AI by itself?

Not necessarily. Atipol, for example, does not, on its own, detect agents or MCP servers installed outside the platform, so organization isolation and audit logs cover what happens inside the platform, not what runs outside it.

Sources

Try it on a real project

The public demo shows a fictional organization at work, no account needed. The free plan includes a project, three agents and an agent lead.