create_settings_object · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_settings_object does on Dynatrace SaaS MCP Server

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

This tool creates and persists settings objects in Dynatrace, modifying system configuration state reversibly. While it includes validation guardrails (validateOnly, dryRun, constraintViolations feedback), it remains a Write operation that modifies observability platform configuration.

From the tool's definition Tool description explicitly states '(WRITE)' and 'Create a Settings 2.0 object' with capabilities to validate and conditionally create settings objects. The dryRun parameter allows safe validation, but the primary action is creating/persisting configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_settings_object Rate-limited

create_settings_object 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_settings_object": {
      "limits": [
        {
          "counter": "create_settings_object_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_settings_object

What does the create_settings_object tool do? +

Create a Settings 2.0 object (WRITE). Validates against the live schema first (validateOnly); returns constraintViolations without creating if invalid. Pass dryRun:true to validate only. 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_settings_object? +

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

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

Can I rate-limit create_settings_object? +

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

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

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