update_filter_segment · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_filter_segment does on Dynatrace SaaS MCP Server

AI agents use update_filter_segment 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_filter_segment needs a policy

This tool creates or modifies data reversibly by updating a filter segment. While it affects configuration data that could impact monitoring and observability queries, the change is reversible (can be updated again or reverted). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or perform irreversible operations.

From the tool's definition Tool description explicitly states 'Update (replace)' which modifies existing data. Categorized as 'WRITE' in the description itself. Operates on 'filter-segments' in platform storage, allowing modification of filter configurations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_filter_segment Rate-limited

update_filter_segment 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_filter_segment": {
      "limits": [
        {
          "counter": "update_filter_segment_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_filter_segment

What does the update_filter_segment tool do? +

Update (replace) a filter segment by UID (WRITE, platform storage filter-segments 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_filter_segment? +

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

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

Can I rate-limit update_filter_segment? +

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

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

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