create_slo · Dynatrace SaaS MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_slo does on Dynatrace SaaS MCP Server

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

Creating an SLO modifies the monitoring configuration in Dynatrace by adding a new service-level objective. While this is a write operation that can be undone (SLOs can be deleted), it affects observability configuration and business metrics tracking.

From the tool's definition Tool description explicitly states '(WRITE)' and describes creating an SLO with configurable fields (name, criteria, target). SLOs are monitoring objectives that can be modified or deleted later, making this a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_slo Rate-limited

create_slo 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_slo": {
      "limits": [
        {
          "counter": "create_slo_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_slo

What does the create_slo tool do? +

Create an SLO (WRITE). Body fields per the SLO v1 spec (name, criteria, target, etc.). 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_slo? +

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

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

Can I rate-limit create_slo? +

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

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

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