Verify before it runs
Nothing takes effect until it has been checked.
Cognilox holds each action an agent takes for the moment it needs: long enough to check it against your rules, try it first if it is risky, and give it the right answer.
Delete inactive customers
Tested first and rolled back. Your rule: large deletes need two people, and never the agent's own owner.
- AAnika Data leadWaiting
- RRohan SecurityWaiting
- MMeera owns this agentCannot approve
- 5kinds of action checked: code, data, infrastructure, tools and replies
- 4answers: allow, fix, hold or block
- 2people can be required for the riskiest changes
- 1exact action per approval, run once
Watch it decide
Every action, checked in the moment before it happens.
Actions arrive from your agents, Cognilox checks who is asking and your rules, tries the risky ones first, and answers. Allowed work flows on. The rest never does.
Checks every action before it runs
- Who is askingIdentity proven
- Your rulesChecked
- Try it firstNot needed
What it checks
Every kind of action an agent can take.
Code and commands
Commands a coding agent runs and the files it changes, before they run.
Learn moreDatabase changes
Every statement, before it reaches your data. Destructive changes stop at the door.
Learn moreInfrastructure changes
Plans that delete data stores, open systems to the internet or widen access, caught first.
Learn moreTool calls
Calls into your CRM, files and internal systems, checked against what each agent may do.
Learn moreReplies
What agents say to customers and colleagues, checked as it is written.
Learn moreModel calls
What agents send to the models they use, and what comes back.
Same day, two endings
Flip the switch.
The same four actions from a data agent, without Cognilox and with it.
A data agent, on an ordinary day
- 1
Delete inactive customers, with the filter missing
Held for approvalTried first: it would remove every row. Waits for two people. - 2
Drop the orders table
BlockedRefused outright, with the reason given to the agent. - 3
Reply to a client with a password in the text
FixedThe password is removed and the reply goes out. - 4
Update a ticket's status
AllowedStraight through, and signed into the record.
Flip the switch to compare the same actions.
In order
Five checks, one decision.
01
It knows who is asking
Every agent proves who it is before it can act. A stolen token or an agent pretending to be another gets nowhere.
02
It checks your rules
The action is held against the rules your company wrote, in words your team can read and change. No hidden rules, ever.
03
It tests the risky ones first
A risky database change is tried out first and rolled back, so you see exactly how much it would change. Infrastructure plans are reviewed before they are applied.
04
It decides
Allowed, fixed, held for approval or blocked. When it blocks, it tells the agent why, so the agent can correct itself instead of guessing.
05
It keeps the proof
Every decision is signed and kept, without the content itself. Any session can be replayed later, step by step.
Questions
About verification.
Code changes and commands, database statements, infrastructure changes, tool calls and the replies agents write. Each one is checked against your company's rules before it takes effect.
For risky database writes, Cognilox tries the change, measures how much it would affect and undoes it, so your rules can act on the real effect. Infrastructure change plans are reviewed before they are applied.
Not if your rules say otherwise. Cognilox can require two approvers and keep the agent's own owner out of the decision. Each approval covers only the exact action approved.
Yes. When Cognilox blocks an action it tells the agent why in words the agent can act on, so it can correct itself instead of retrying blindly.
See it stop an attack, live.
Thirty minutes, real agents, real attacks. We show you what Cognilox allows, fixes, holds and blocks, then talk through your own agents.