Validate a DQL processor script without mutating any configuration (safe, read-only).
AI agents call verify_openpipeline_dql_processor to retrieve information from Dynatrace SaaS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation/verification of a DQL processor script purely for checking correctness. No configuration is created, modified, or deleted. The description explicitly confirms it is read-only and safe. The worst-case misuse is generating false validation results, which has minimal blast radius. Classification as Read with low severity is appropriate.
From the tool's definition Tool description explicitly states 'Validate a DQL processor script without mutating any configuration (safe, read-only)'. The verb 'Validate' and phrase 'read-only' indicate no side effects or data modification.
Attacks that exploit this kind of access
Validate a DQL processor script without mutating any configuration (safe, read-only). It is categorised as a Read tool in the Dynatrace SaaS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for verify_openpipeline_dql_processor: 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.
verify_openpipeline_dql_processor is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the verify_openpipeline_dql_processor 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.
Set action: deny in the PolicyLayer policy for verify_openpipeline_dql_processor. 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.
verify_openpipeline_dql_processor 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →