Agent governance

Every agent call is checked before it runs.

Cortega sits between your agents and everything they touch — LLMs, MCP tools, databases, APIs. Two deterministic checks run on every call before it executes.

Tool call GATE 1 Access check: is this agent allowed to call this tool? pass GATE 2 Argument check: do the arguments violate policy? pass Execute Blocked fail fail Both checks are deterministic.
What it governs

Four controls

01

Identity and access

Every request carries verified identity (JWT, mTLS, OAuth 2.0). Virtual keys with create, rotate, expire, revoke. Full RBAC and SSO in the base product.

02

Policy enforcement

Two layers on every tool call: is this agent allowed to call this tool, and do the arguments violate policy. Both must pass. Both fail closed.

03

Egress governance

Per-team, per-agent allow lists for providers and models. Deterministic PII and PCI detection before a request leaves. Output scanning on the return path.

04

Budgets and spend

Team and provider budgets as hard blocks. Rate limiting per principal. Denial-of-Wallet detection on token velocity and loop signatures.

In the console

One policy

Model access — per-team allow lists
Model access
Guardrails
Observability

From the Cortega console.

By default

Least privilege

01

Task-scoped permissions

Agents get only the permissions the current task needs, for the duration of that task.

02

Every inter-agent call authorized

Inter-agent calls are checked against per-identity policy before they proceed. Delegation limits enforced.

03

Approval on consequential actions

Before a consequential action, a plain-English summary and a documented approval decision in the audit log.

MAKE YOUR NEXT MOVE

Book a demo

Explore how Cortega fits your AI environment.

Request a demo Learn more Explore the Cortega documentation