classify_incident
Assess ICT incidents against DORA thresholds to identify major incidents requiring 4h/72h/1-month reporting.
Instructions
Classify an ICT incident against DORA major-incident thresholds per Commission Delegated Regulation (EU) 2024/1772. Returns whether it qualifies as a 'major ICT incident' requiring 4h/72h/1-month reporting.
Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.
When to use: Use this tool when you need to assess, audit, or verify compliance requirements. Ideal for gap analysis, readiness checks, and generating compliance documentation.
When NOT to use: Do not use as a substitute for qualified legal counsel. This tool provides technical compliance guidance, not legal advice.
Args: incident_description (str): The incident description to analyze or process. clients_affected (int): The clients affected to analyze or process. duration_hours (float): The duration hours to analyze or process. economic_impact_eur (float): The economic impact eur to analyze or process. data_loss (bool): The data loss to analyze or process. api_key (str): The api key to analyze or process.
Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| incident_description | Yes | ||
| clients_affected | No | ||
| duration_hours | No | ||
| economic_impact_eur | No | ||
| data_loss | No | ||
| api_key | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |