run_workflow · Dynatrace SaaS MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_workflow does on Dynatrace SaaS MCP Server

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

While the description uses the label 'WRITE', the actual capability is to trigger/execute a workflow, which is Execute-class behavior. Workflows in automation platforms typically perform actions that extend beyond simple data creation (they may invoke APIs, modify multiple systems, trigger external operations, etc.).

From the tool's definition Tool description states 'Trigger a run of a Dynatrace Automation workflow' — it executes an external automated workflow whose effects depend on what that workflow contains and performs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_workflow Rate-limited

run_workflow 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": {
    "run_workflow": {
      "limits": [
        {
          "counter": "run_workflow_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 run_workflow

What does the run_workflow tool do? +

Trigger a run of a Dynatrace Automation workflow (WRITE, platform Automation v1). 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 run_workflow? +

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

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

Can I rate-limit run_workflow? +

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

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

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