create_request_attribute · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_request_attribute does on Dynatrace SaaS MCP Server

AI agents use create_request_attribute 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_request_attribute needs a policy

This tool creates a new request attribute in Dynatrace configuration, which is a reversible write operation. It modifies system configuration but does not delete data, execute arbitrary code, or affect financial systems. The blast radius is medium because misconfigured request attributes could affect monitoring scope or data collection, but the operation can be undone or corrected.

From the tool's definition Tool description explicitly states "Create a new request attribute (WRITE, classic Config API v1)". The WRITE designation and "create" verb indicate data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_request_attribute Rate-limited

create_request_attribute 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_request_attribute": {
      "limits": [
        {
          "counter": "create_request_attribute_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_request_attribute

What does the create_request_attribute tool do? +

Create a new request attribute (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 create_request_attribute? +

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

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

Can I rate-limit create_request_attribute? +

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

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

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