Delete a self-notification by ID (WRITE, destructive, platform notification v1).
AI agents call delete_self_notification 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 irreversibly deletes data (a self-notification) and cannot be undone. While the blast radius is limited to a single notification rather than system-wide data, deletion operations are categorized as Destructive per the classification rules. The explicit 'destructive' label in the description confirms this assessment.
From the tool's definition Tool description explicitly states 'Delete' and 'destructive'; removes a notification resource by ID with no undo mechanism.
Attacks that exploit this kind of access
Delete a self-notification by ID (WRITE, destructive, platform notification 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.
Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for delete_self_notification: 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_self_notification 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_self_notification 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_self_notification. 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_self_notification 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 →