update_openpipeline_configuration

WHAT IT DOES

What update_openpipeline_configuration does on Dynatrace SaaS MCP Server

AI agents use update_openpipeline_configuration to create or update resources in Dynatrace SaaS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynatrace SaaS MCP Server environment.

WHY IT NEEDS A POLICY

Why update_openpipeline_configuration needs a policy

This tool modifies configuration settings reversibly (a new configuration can replace the old one, and prior configurations can be restored). While it has significant operational impact—misconfigured pipelines could lose or misdirect observability data—it is not irreversible destruction of data itself, nor does it directly execute arbitrary code or move money.

From the tool's definition Tool description explicitly states 'Replace the full OpenPipeline configuration' and is marked 'WRITE'. OpenPipeline is a Dynatrace data processing system; replacing its configuration affects how ingested data is processed and routed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_openpipeline_configuration Rate-limited

update_openpipeline_configuration stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_openpipeline_configuration": {
      "limits": [
        {
          "counter": "update_openpipeline_configuration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_openpipeline_configuration

What does the update_openpipeline_configuration tool do? +

Replace the full OpenPipeline configuration for a specific data type (WRITE, requires DT_ENABLE_WRITES=true). It is categorised as a Write tool in the Dynatrace SaaS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_openpipeline_configuration? +

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

update_openpipeline_configuration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_openpipeline_configuration? +

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

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

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