AI Aulis

AI NEWS IN ENGLISH · 15 November 2026

The most important AI news every morning. AI writes and checks the stories against the original sources – check important facts in the sources.

26 stories · next issue tomorrow morning · How the paper is made →

← Issue 15 November 2026Paper

Dynatrace MCP server’s read tools let callers inject their own DQL query stages

AI-generated contentWritten by AI

github.com, i10x.ai · 2 sources · Sources published: 13 November 2026 · Some source publication dates are unknown

The read tools in Dynatrace MCP Server inserted caller-supplied values into queries without sufficient checks, so tools whose calls some MCP clients approve without asking the user could run more than they were meant to. According to i10x, version 2.1.1 contains the fix.

On 13 November the AI news site i10x.ai reported a now-fixed injection vulnerability in Dynatrace’s MCP server, tracked as CVE-2026-123810. Dynatrace had already published security advisory GHSA-pqh8-p93p-2rx7 about it on 9 June, the site said. It put the severity at medium (CVSS 4.3).

Dynatrace MCP Server is an MCP server, a program that an AI agent uses to retrieve data from Dynatrace’s monitoring service.

How the injection worked

Five of the server’s read tools built queries in DQL, Dynatrace’s own query language, and inserted caller-supplied values into them without sufficient checks. These values included the names of monitored entities, the timeframe and cluster identifiers. According to i10x, a suitably crafted value could close a string, add new stages to the query or skip the rest of the query with a // comment. In the site’s example, the timeframe value ‘30d, to: now() | fieldsAdd internal_secret //’ adds a stage of its own before the tool’s filter.

This let a caller bypass the tools’ limits on which fields are returned, which time period is covered and how many results are shown. The tools carried the readOnlyHint annotation, which indicates that a tool changes nothing. Some MCP clients approve calls to such tools without asking the user. i10x assessed that an attacker would typically exploit the flaw through prompt injection, hiding instructions in content that the language model reads.

However, the flaw gave no access to data that the user’s token could not already reach, i10x said. The site, summarising the advisory, said the same token also gives access to the execute_dql tool, which can run any DQL query. The harm, then, is that neither the limits the read tools promised nor automatic approval could be relied on. Access rights did not expand.

What the fix prevents

The fix is in GitHub commit 15d3546, made on 14 July according to i10x. The commit adds three checks. The timeframe must be a positive integer and a unit, such as 24h or 7d. The additional filter must not contain a pipe character or a line break. Backslashes and quotation marks in values embedded in strings are escaped with a backslash so that a value cannot close the string. Each of the five files received the checks relevant to it.

A code comment says the additional filter check does not block subqueries written in square brackets, such as x in [fetch ...]. Each tool’s OAuth permissions limit these, and the developers consider this acceptable and intentional.

i10x said the flaw affects versions up to and including 1.8.5, and the site advises upgrading to version 2.1.1 or newer. It does not say whether the versions in between are affected.

Report an error in this story