Delete a request naming rule by ID (WRITE, destructive, classic Config API v1).
AI agents call delete_request_naming 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.
Deleting a request naming rule is an irreversible operation that cannot be undone. This falls squarely under Destructive category per the classification rules. While the blast radius is somewhat contained (affecting only observability configuration rather than data or financial systems), deletion of monitoring configuration rules could impact system visibility and alerting, warranting high severity.
From the tool's definition Tool description explicitly states 'Delete a request naming rule by ID' combined with '(WRITE, destructive, classic Config API v1)'. The descriptor 'destructive' in the tool description itself confirms irreversible deletion.
Attacks that exploit this kind of access
Delete a request naming rule by ID (WRITE, destructive, classic Config API 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_request_naming: 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_request_naming 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_request_naming 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_request_naming. 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_request_naming 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 →