update_request_naming · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_request_naming does on Dynatrace SaaS MCP Server

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

This tool reversibly modifies an existing request naming rule configuration in Dynatrace. While it changes system behavior (how requests are named/categorized), the change is non-destructive and can be undone by reverting to previous configuration. The blast radius is medium: incorrect naming rules could degrade observability or cause confusion in monitoring dashboards, but do not cause data loss or financial impact.

From the tool's definition Tool description explicitly states 'Update an existing request naming rule' and is marked '(WRITE, classic Config API v1)'. The action modifies configuration without deleting or creating new rules.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_request_naming Rate-limited

update_request_naming 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_request_naming": {
      "limits": [
        {
          "counter": "update_request_naming_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_request_naming

What does the update_request_naming tool do? +

Update an existing request naming rule by ID (WRITE, classic Config API 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 update_request_naming? +

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

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

Can I rate-limit update_request_naming? +

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

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

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