update_settings_object · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_settings_object does on Dynatrace SaaS MCP Server

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

This tool creates or modifies settings configurations in Dynatrace reversibly. While it can change observability configurations (dashboards, monitors, SLOs, etc.), the built-in validation (validateOnly, dryRun flags) and reversible nature of settings updates place it in Write rather than Execute.

From the tool's definition Tool description explicitly states 'Update an existing Settings 2.0 object' with validation capability. The '(WRITE)' designation and dryRun option confirm write-class semantics. 'Update' modifies configuration data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_settings_object Rate-limited

update_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": {
    "update_settings_object": {
      "limits": [
        {
          "counter": "update_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 update_settings_object

What does the update_settings_object tool do? +

Update an existing Settings 2.0 object by objectId (WRITE). Validates against the live schema first (validateOnly); returns constraintViolations without updating 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 update_settings_object? +

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

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

Can I rate-limit update_settings_object? +

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

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

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