verify_dql · Dynatrace SaaS MCP Server MCP: Risk & Policy

WHAT IT DOES

What verify_dql does on Dynatrace SaaS MCP Server

AI agents invoke verify_dql to trigger actions in Dynatrace SaaS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why verify_dql needs a policy

Although the tool runs with limit 0 and returns no data, it still executes a query against the live system. This is an Execute action (running a query/statement), not merely a Read, since it triggers external execution. The blast radius is low because no data is returned and no state is modified — it is purely a validation/syntax-check execution.

From the tool's definition 'Validate a DQL statement without returning data (executes with limit 0)' — the tool actively executes a DQL statement against the Dynatrace backend

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verify_dql Rate-limited

verify_dql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_dql": {
      "limits": [
        {
          "counter": "verify_dql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dynatrace SaaS MCP Server, so you can run agents against it safely.

FAQ

Questions about verify_dql

What does the verify_dql tool do? +

Validate a DQL statement without returning data (executes with limit 0). It is categorised as a Execute tool in the Dynatrace SaaS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on verify_dql? +

Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for verify_dql: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Dynatrace SaaS MCP Server. Nothing to install.

What risk level is verify_dql? +

verify_dql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit verify_dql? +

Yes. Add a rate_limit block to the verify_dql rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block verify_dql completely? +

Set action: deny in the PolicyLayer policy for verify_dql. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides verify_dql? +

verify_dql is provided by the Dynatrace SaaS MCP Server MCP server (mnmozi/dynatrace-mcp-saas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.