preview_openpipeline_pipeline

WHAT IT DOES

What preview_openpipeline_pipeline does on Dynatrace SaaS MCP Server

AI agents invoke preview_openpipeline_pipeline 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 preview_openpipeline_pipeline needs a policy

This tool executes a pipeline simulation by running a record through a sequence of processors. While it is likely read-only/non-destructive in nature (a 'preview'), it actively executes processing logic against data, making it an Execute category. The blast radius is medium since it's a preview operation but still runs computational logic that could expose or misprocess sensitive observability data.

From the tool's definition Preview the effect of an ORDERED SEQUENCE of processors by threading a record through each one

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

preview_openpipeline_pipeline Rate-limited

preview_openpipeline_pipeline 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": {
    "preview_openpipeline_pipeline": {
      "limits": [
        {
          "counter": "preview_openpipeline_pipeline_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 preview_openpipeline_pipeline

What does the preview_openpipeline_pipeline tool do? +

Preview the effect of an ORDERED SEQUENCE of processors by threading a record through each one. 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 preview_openpipeline_pipeline? +

Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for preview_openpipeline_pipeline: 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 preview_openpipeline_pipeline? +

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

Can I rate-limit preview_openpipeline_pipeline? +

Yes. Add a rate_limit block to the preview_openpipeline_pipeline 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 preview_openpipeline_pipeline completely? +

Set action: deny in the PolicyLayer policy for preview_openpipeline_pipeline. 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 preview_openpipeline_pipeline? +

preview_openpipeline_pipeline 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.