delete_filter_segment

Delete a filter segment by UID (WRITE, destructive, platform storage filter-segments v1).

Server Dynatrace SaaS MCP Server mnmozi/dynatrace-mcp-saas
Category Destructive
Risk class Critical
Parameters 00 required

What delete_filter_segment does on Dynatrace SaaS MCP Server

AI agents call delete_filter_segment to permanently remove resources in Dynatrace SaaS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_filter_segment needs a policy

This tool permanently removes a filter segment from Dynatrace platform storage. Filter segments are likely used across dashboards, queries, and monitoring configurations. Deletion cannot be undone and could break dependent workflows or dashboards. While not causing financial impact or executing arbitrary code, the irreversible data loss qualifies this as Destructive rather than Write.

From the tool's definition Tool description explicitly states 'Delete a filter segment by UID' and marks it as '(WRITE, destructive, platform storage filter-segments v1)'. The delete operation on filter segments is irreversible.

Questions about delete_filter_segment

What does the delete_filter_segment tool do? +

Delete a filter segment by UID (WRITE, destructive, platform storage filter-segments v1). It is categorised as a Destructive tool in the Dynatrace SaaS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_filter_segment? +

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

delete_filter_segment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_filter_segment? +

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

Set action: deny in the PolicyLayer policy for delete_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 delete_filter_segment? +

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.