Cancel a Grail record deletion process that is in progress or queued.
AI agents call cancel_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.
While 'cancel' sounds like it prevents destruction, this tool directly interacts with a deletion process. However, canceling a deletion is actually a protective/reversal action — it stops an ongoing destructive operation. That said, the tool is still deeply entangled with a destructive workflow (record deletion).
From the tool's definition Cancel a Grail record deletion process that is in progress or queued
Attacks that exploit this kind of access
Cancel a Grail record deletion process that is in progress or queued. 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 cancel_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.
cancel_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 cancel_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 cancel_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.
cancel_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 →