Triage alerts, stay in charge of containment.
For CISOs and SOC analysts: agents triage alerts read-only, and containment actions always wait for an analyst's approval.
The problem
Many alerts are never investigated for lack of time. Triage is done by hand, one alert at a time.
Handing triage to an unframed agent only moves the risk: an agent that can lock an account or isolate a machine without human approval is the tool and privilege abuse OWASP lists among the risks specific to agents.
How Atipol handles it
A workflow starts on every alert and hands triage to a dedicated agent.
The triage agent queries the SIEM through MCP, read-only, and opens a ticket with its summary.
Containment tools (locking an account, isolating a machine) are set to approval: the call waits for the analyst's decision, for that specific call and only once.
Everything is recorded in the log: every tool call with its result, every approval with its author.
What you measure
- Time to pick up each alert.
- The share of qualified alerts.
- The cost per alert, estimated from the tokens of each run.
Frequently asked questions
What happens if the agent wants to lock an account?
If the tool is set to approval, the call waits for a person to decide. If it is forbidden, the call is refused and logged.
Can the triage agent change the SIEM?
Not unless you allow it: every tool is allowed, subject to approval or forbidden, and a new tool arrives forbidden. For triage, the agent only has read tools.
How do I stop an agent?
From the console: you stop its run, revoke its identity or remove a tool, without touching the other agents.
Try it on a real project
The public demo shows a fictional organization at work, no account needed. The free plan includes a project, three agents and an agent lead.