Delete a specified monitoring configuration for an Extension 2.0 (WRITE, destructive).
AI agents call delete_extension_monitoring_config 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.
This tool permanently removes monitoring configuration for an Extension 2.0, which cannot be undone. Although the blast radius is limited to a single extension's config (not system-wide), the destructive nature and potential operational impact (loss of visibility/monitoring) warrant 'high' severity. Classified as Destructive rather than Write because deletion is irreversible.
From the tool's definition Tool name contains 'delete'; description explicitly states 'Delete a specified monitoring configuration' and labels it '(WRITE, destructive)'. The irreversible removal of extension monitoring configuration is destructive.
Attacks that exploit this kind of access
Delete a specified monitoring configuration for an Extension 2.0 (WRITE, destructive). 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.
Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for delete_extension_monitoring_config: 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.
delete_extension_monitoring_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_extension_monitoring_config 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.
Set action: deny in the PolicyLayer policy for delete_extension_monitoring_config. 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.
delete_extension_monitoring_config 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.
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 →