DESTRUCTIVE — permanently deletes Grail records matching the given DQL query and optional timeframe.
AI agents call execute_record_deletion 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 deletes data without ability to undo the action, matching the Destructive category definition. The 'permanently deletes' language and explicit DESTRUCTIVE label confirm irreversibility. The blast radius is critical because an AI agent with access could delete entire Grail record sets matching arbitrary DQL queries, causing permanent data loss in the observability platform.
From the tool's definition Tool description explicitly states 'DESTRUCTIVE — permanently deletes Grail records' and the name 'execute_record_deletion' indicates irreversible deletion of data.
Attacks that exploit this kind of access
DESTRUCTIVE — permanently deletes Grail records matching the given DQL query and optional timeframe. 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 execute_record_deletion: 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.
execute_record_deletion 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 execute_record_deletion 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 execute_record_deletion. 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.
execute_record_deletion 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 →