update_feature_flag · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_feature_flag does on Dynatrace SaaS MCP Server

AI agents use update_feature_flag 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_feature_flag needs a policy

This tool creates or modifies feature flag data reversibly. While feature flags control application behavior and could have broad impact if misconfigured by an agent, the operation is not inherently destructive (can be reverted), not financial, and does not execute arbitrary code.

From the tool's definition Tool name 'update_feature_flag' and explicit description marking it as '(WRITE)' indicate modification of feature flag configuration state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_feature_flag Rate-limited

update_feature_flag 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_feature_flag": {
      "limits": [
        {
          "counter": "update_feature_flag_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_feature_flag

What does the update_feature_flag tool do? +

Update a feature flag by key (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 update_feature_flag? +

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

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

Can I rate-limit update_feature_flag? +

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

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

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