A seven-stage review of one caller-declared agent incident across three regulatory regimes. Step 1 composes a structured incident record from the declared agent identity, incident description with its severity class, session evidence digests and remediation status (art-379). Step 2 then classifies the autonomy tier and the in-force AI Act obligations the declared deployment carries (art-67). Step 3 then applies the DORA major-incident numeric criteria to the declared impact figures and reports a major or non-major classification with the reporting clock a major finding starts (art-467). Step 4 then scores the declared disruption, affected-user and loss figures against the NIS2 significance criteria and reports a significance verdict (art-144). Step 5 then starts the clock obligations for the regimes the caller declares applicable from one determination timestamp (art-428). Step 6 then builds the post-market monitoring, logging and oversight plan for the declared high-risk deployment as a decision-support draft (art-66). Step 7 then validates the declared agent audit-trail records and returns a conformance result (art-237). Each step computes from its own declared inputs; the order is a review sequence, not a statutory one, and the chain determines no reporting obligation.
build_agent_incident_record{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "build_agent_incident_record",
"arguments": {}
},
"id": 1
}
classify_agentic_ai_risk{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "classify_agentic_ai_risk",
"arguments": {}
},
"id": 1
}
classify_dora_ict_incident_and_clock_deadlines{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "classify_dora_ict_incident_and_clock_deadlines",
"arguments": {}
},
"id": 1
}
score_nis2_incident_significance{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "score_nis2_incident_significance",
"arguments": {}
},
"id": 1
}
compute_cyber_incident_notification_clock{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "compute_cyber_incident_notification_clock",
"arguments": {}
},
"id": 1
}
build_fria_monitoring_plan{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "build_fria_monitoring_plan",
"arguments": {}
},
"id": 1
}
validate_agent_audit_trail{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_agent_audit_trail",
"arguments": {}
},
"id": 1
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: An agent outage disrupted service for four hours and hit 5,000 users. Does the NIS2 scorer call the incident significant, and do reporting clocks start?
Run the AINumbers MCP tool `run_chain` with {"chain":"ai-agent-incident-multi-regime"} and read `art-144-nis2-incident-significance-scorer.significance_verdict`.
Re-run with `inputs` for `art-144-nis2-incident-significance-scorer`, reusing the values that result echoed, with `service_disruption_hours` set to 0.5. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/ai-agent-incident-multi-regime.html