create_monitor · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_monitor does on Dynatrace SaaS MCP Server

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

Creating a synthetic monitor is a write operation that adds a new monitoring configuration to Dynatrace. While it modifies system state, it is reversible (the monitor can be deleted or updated), does not execute arbitrary code on monitored systems, and does not involve financial transactions or irreversible data destruction.

From the tool's definition Tool description explicitly states '(WRITE)' and the name 'create_monitor' indicates creation of a new synthetic monitor definition, which is a reversible configuration change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_monitor Rate-limited

create_monitor 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_monitor": {
      "limits": [
        {
          "counter": "create_monitor_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_monitor

What does the create_monitor tool do? +

Create a new synthetic monitor definition (WRITE). 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_monitor? +

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

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

Can I rate-limit create_monitor? +

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

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

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