create_feature · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_feature does on Dynatrace SaaS MCP Server

AI agents use create_feature 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_feature needs a policy

This tool creates new data (a feature) in the Dynatrace platform, which is a Write operation. It is reversible—features can be subsequently modified or deleted—so it does not qualify as Destructive. The blast radius is medium because creating unintended features in a project could clutter the configuration and potentially affect feature flag behavior, but does not directly cause data loss or financial impact.

From the tool's definition Tool name 'create_feature' and description explicitly marked '(WRITE)' indicates data creation. The tool creates a feature in a project, which is a reversible operation (features can be modified or deleted).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_feature Rate-limited

create_feature 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_feature": {
      "limits": [
        {
          "counter": "create_feature_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_feature

What does the create_feature tool do? +

Create a feature in a project (WRITE). 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_feature? +

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

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

Can I rate-limit create_feature? +

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

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

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