create_workflow · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_workflow does on Dynatrace SaaS MCP Server

AI agents use create_workflow 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 create_workflow needs a policy

Creating an automation workflow establishes new automated processes that can trigger actions across the Dynatrace platform. While reversible (workflows can be deleted), a miscreated workflow could trigger unintended automated actions at scale, giving it a high severity blast radius. The tool itself is a Write operation as it creates/registers a new resource.

From the tool's definition 'Create a Dynatrace Automation workflow (WRITE, platform Automation v1)' — explicitly labeled WRITE and creates a new automation workflow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_workflow Rate-limited

create_workflow 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": {
    "create_workflow": {
      "limits": [
        {
          "counter": "create_workflow_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 create_workflow

What does the create_workflow tool do? +

Create a Dynatrace Automation workflow (WRITE, platform Automation v1). 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 create_workflow? +

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

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

Can I rate-limit create_workflow? +

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

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

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