When invoking splunk_run_query via the Splunk MCP server, tool calls consistently fail with: MCP error -32001: AbortError: This operation was aborted. This is not model-specific — the same failure is observed with any LLM The identical abort/timeout behavior also occurs when running queries manually outside of an LLM workflow. Configure Splunk MCP server in the environment. Invoke splunk_run_query with any valid SPL query (via LLM tool call or manual invocation). Observe the tool call failure with error: MCP error -32001: AbortError: This operation was aborted . Tool call fails with a generic MCP error -32001: AbortError . No indication of whether this is a client abort, server timeout, or licensing constraint. The workflow cannot proceed. Has anyone encountered MCP error -32001: AbortError with the Splunk MCP server? What was the root cause? Are there known Splunk license tier restrictions that affect MCP server query execution? Is there a configurable timeout parameter for the Splunk MCP server's query execution (e.g., max_query_time , transport_timeout )? Does the MCP server respect dispatch.ttl or max_time settings from limits.conf ? ... View more