Watchlight AI

Answers

AI agent governance, answered

Short answers to the questions identity and security teams ask about putting AI agents into production.

What is Agent Runtime Governance?

Agent Runtime Governance (ARG) is the discipline of controlling what autonomous AI agents do while they run. It decides each governed action against policy before it executes, keeps authority scoped to the task, contains an agent that goes off course, and records what was decided. Watchlight AI defined the category in February 2026.

Read the full definition

What is Agentic IAM?

Agentic IAM is the identity architecture for AI agents. It extends your IAM, PAM, and IGA to cover how people delegate to agents, how agents delegate to each other, how agents reach tools and MCP servers, and how that authority is narrowed, expired, and revoked.

See the Agentic IAM Architecture engagement

How is Agent Runtime Governance different from IAM?

IAM establishes who an agent is and what it can reach. Agent Runtime Governance decides whether a specific action should happen now, for this task, under this authority. The two work together: identity stays the foundation, and governance acts on what the agent does with the access it holds.

Read more on identity and governance

How do you authorize AI agents?

Authorize each action at the moment it runs. Scope authority to the task, evaluate the action against deterministic policy outside the agent, and refuse what falls outside the scope. A valid token shows the agent can reach a system. It does not show this action should happen.

See how authorization works

How do you secure agent-to-agent delegation?

Make every handoff produce authority equal to or narrower than what the parent holds, in actions, resources, and time, and refuse any request for more. Build the chain from records the agent cannot edit, so a sub-agent cannot claim authority it was never given.

See the delegation use case

How do you stop an AI agent mid-run?

You need responses beyond allow and deny, written into policy ahead of time. Stop the run, quarantine the agent until an operator releases it, cut off the sub-agents it started, or revoke its trust. Each reaches a different scope, so you can act without taking down a whole workflow.

See containment

How do you audit what AI agents did?

Record each decision when it is made, along with the run and sub-agent it belongs to, the policy that decided it, and the reason. Logs stitched together after an incident show timing. A record written at decision time shows why an action was allowed or refused.

See execution lineage

How do you govern MCP servers and tool calls?

Know which MCP servers and agents exist, assign each an owner and an identity, then evaluate tool calls against policy before they execute. Enforcing in two places helps: an in-process plugin sees the agent's plan and intent, and a proxy governs traffic on the wire.

See agent and MCP discovery

Are AI guardrails the same as Agent Runtime Governance?

No. Guardrails mostly inspect what goes into and comes out of a model. Agent Runtime Governance acts on what the agent then tries to do: its tool calls, its delegations, and its authority across a run. Many teams use both.

See what sets Watchlight apart

What is an AI agent control plane?

An agent control plane is the layer that sits outside your agents and governs them across frameworks: identity, policy, enforcement, containment, and evidence. Watchlight AI Beacon is the control plane for Agent Runtime Governance.

Explore Watchlight AI Beacon

Should an LLM make authorization decisions for agents?

No. An authorization decision should be deterministic, so the same request under the same policy gets the same answer and a model cannot be talked out of it. Watchlight AI Beacon keeps language models out of the authorization decision.

See the architecture

Which compliance frameworks apply to AI agents?

ISO/IEC 42001, NIST AI RMF, and the EU AI Act are the usual starting points, and all three expect controls you can demonstrate. The Agent Compliance Map shows how Beacon enforces and evidences agent controls across nine frameworks and 73 requirements.

Open the Agent Compliance Map

Does a governance product make you compliant?

No. Compliance belongs to your whole program, and your auditor decides. A product can enforce the agent controls that program requires and produce evidence for them. The Agent Compliance Map marks which requirements Beacon supports and how.

Open the Agent Compliance Map

How do you start governing AI agents?

Pick one real agent workflow, assess its fit and readiness, then pilot governance on it before you deploy widely. Developers can start with Watchlight Developer Edition, which is free and open source and runs on their own machine.

See the assessment

Ready to Get Started?

Govern the authority behind every AI agent action

Watchlight AI Beacon is available now, ready to install in your environment, on-premises or air-gapped. See it decide, enforce, and prove agent actions at runtime.

We typically respond within one business day.

We value your privacy

We use cookies for analytics and to remember your preferences. Learn more ·