Read in step 2, acted on in step 7.
A tool that looks at one call at a time cannot see this chain. AvertGate gathers every call in a session into one record, so a poisoned document and the action built on it appear side by side.
Decision flow
The record cannot be altered
send_emailsession 4f2a · #7- Linked to content flagged in step 2
- Event chained to the previous one
- SHA-256 digest written
Single calls can look harmless.
A slow leak is split into small pieces; a loop is made of hundreds of harmless calls. None of them alarms on its own.
Collect
Every call lands in the same record with its agent and session identity.
Link
Events are chained with SHA-256; each one is tied to the one before.
Review
Open a session in the dashboard and follow the decision and its reason event by event.
See it. Limit it. Prove it.
An attack in seven steps.
Poisoned content is read and flagged; the next action is caught in the same session.
- Session context. Events from the same session are evaluated together.
- Accumulated signals. Small leak attempts are counted and stopped once the threshold is crossed.
- Loop breaker. An agent that repeats the same call is stopped at some point.
Audit trail
Every call in the live stream.
Take the rules out of code.
Allow, limit and approval rules per tool and argument live in a single YAML file. A change needs no redeploy.
- Deny by default. A tool that is not listed does not run.
- Argument limits. Fields such as amount, SQL and URL are bound to a rule.
- Human approval. Risky calls wait for approval in Slack.
Policy editor
The rule is written on one screen.
Every decision is recorded.
The decision, reason and rule id are linked with SHA-256; a record changed afterwards is detected.
- Reasoned decision. Every event carries the reason and rule id.
- Redacted arguments. Raw data never reaches the dashboard.
- Session trail. Calls in the same session are read together.
Session trails
Every session is traced end to end.
Audit trail
Every call on record with its decision and reason.
Frequently asked
Where is the audit record stored?
Raw calls stay in the Data Plane in your network. Only redacted events are sent to the dashboard.
What does the chain prove?
That the record was not edited afterwards. Removing or altering one event invalidates every later digest.
How long are old records kept?
The retention period is set together with you during setup.
Guarantees
Four fixed principles behind every decision.
- 3 decisionsEvery call ends in allow, block or human approval.
- Fail-closedIf a check errors, the call is not run.
- SHA-256 chainEvents are chained, so any change after the fact is noticed.
- Your data stays with youTool calls and results never leave your network.
Put a gate in front of your agents.
Every deployment starts with a demo and a POC on your own agents.