One layer every agent action has to cross.
The control plane sits between your agent runtime and everything it wants to touch. Nothing reaches a model, a tool, or a database without producing a decision and a record. It is the operational home of AI agent authorization.
Not a wrapper.
A checkpoint.
An agent asks to do something. The control plane decides, records the decision, and only then lets the action proceed — or does not. That decision is the core of AI agent security at Cirvix.
Intercept
Every execution event arrives as a typed request: which agent, which org, which action, against which policy. Nothing is inferred from the call site.
Evaluate
The policy engine resolves the applicable rules and returns exactly one verdict. Evaluation happens before the action, not as a review afterwards.
Bind
The verdict is bound to the request that produced it. A changed request is a new decision — an old approval cannot be reused for new arguments.
Record
The decision enters a hash-linked audit chain. The record covers the decision; unsanctioned payload data is discarded rather than stored.
Release
Only an allowed action continues to the provider, tool, or database, carrying the tenant scope it was granted.
“Valid identity. Valid credential. Valid tool. Unauthorized consequence → CIRVIX blocks it.”
When autonomous agents act, security cannot rely on human review or post-incident SIEM alerts. Cirvix operates at machine speed (<1.2ms design target), enforcing delegated authority against the effective side effect before any external mutation, cross-resource pivot, or sub-agent escalation can execute.
Where it sits.
Inputs arrive from any runtime you already use. Outputs are reached only through a sanctioned path.
Cirvix Control Plane
Three parts,
one decision.
Each part is separately inspectable. None of them is optional.
Policy Engine
Rules resolve to one verdict before an action runs. Order is deterministic and audit_only never authorizes.
→EvidenceAudit Chain
SHA-256 linked blocks. Any edit to an earlier record breaks every hash that follows it.
→BoundaryDeployment
Docker Compose, Helm, or bare Node — inside whichever network boundary you already trust.
→See a verdict change in front of you
Toggle a rule and watch the decision, the terminal, and the audit block move together.
Bring every agent
under control.
Set durable policy, preserve a verifiable record, and give teams a safer way to put intelligent systems to work.