Known limitations
The following limitations are known from the current ITSI design and MCP Server behavior.
The following limitations are known from the current ITSI design and MCP Server behavior.
| Area | Limitation | Impact |
|---|---|---|
| Client routing | MCP-compatible clients vary in how they route free-form prompts to tools. | Users may need to provide precise episode IDs or ask specific questions such as "get impacted objects" or "find similar episodes." |
| Episode summarization | The summarization tool retrieves stored Event iQ episode summarization. It does not generate a new episode summary on demand. | If Event iQ Episode Summarization is not enabled or no summary exists, summary output is unavailable. |
| Feature scope | The current release is read-oriented. Ticket linking and downstream remediation actions are not in scope. | The integration helps with investigation, but users must complete follow-up actions in ITSI or the relevant external system. |
| Performance | Some episode data retrieval paths depend on searches, aggregations, and stack health. | Tool response times may vary based on data volume, saved search performance, MCP timeout settings, and platform load. |
| MCP guardrails | MCP Server may enforce timeouts, row limits, global rate limits, and server-level tool enablement. | Large result sets or rapid repeated tool calls may be limited or fail. |
Additional references
For additional context, see the following resources: