Incident: open and start the clocks
incident_openOpen a security or operations incident. Privi starts the notification clocks for the rules you pick (GDPR 72 hours, NIS2 24 hours / 72 hours / one month, SEC four business days, your contract's hours) and writes the incident to your tamper-evident 'incidents' log. Requires the organization API key.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>",
"severity": "<severity>",
"actor": "<actor>"
},
"name": "incident_open"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actor | Yes | Who is doing this (person or agent) | |
| title | Yes | What happened, in a sentence | |
| regimes | No | Notification rules that may apply: gdpr = EU GDPR Article 33 (personal data breach); nis2 = EU NIS2 Article 23 (significant incident); sec_8k = US SEC Form 8-K Item 1.05 (material cybersecurity incident) | |
| aware_at | No | When you became aware (ISO 8601). Default: now | |
| severity | Yes | low|medium|high|critical | |
| material_at | No | SEC only: when you decided the incident was material | |
| contract_hours | No | Hours your customer contracts give you to notify them |