delete_resource_file

Delete a file from the Grail Resource Store by path (WRITE, destructive, Resource Store v1).

Server Dynatrace SaaS MCP Server mnmozi/dynatrace-mcp-saas
Category Destructive
Risk class Critical
Parameters 00 required

What delete_resource_file does on Dynatrace SaaS MCP Server

AI agents call delete_resource_file 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.

Why delete_resource_file needs a policy

Deletion of files is an irreversible operation that cannot be undone. Even though the description acknowledges it as 'WRITE', the destructive nature of file deletion places this in the Destructive category, which takes precedence. The impact depends on what files are targeted (blast radius is high if critical resource files are deleted), but the operation itself is definitionally destructive.

From the tool's definition Tool description explicitly states 'Delete a file' and marks it as 'destructive' and 'WRITE'. The action removes data from the Grail Resource Store irreversibly.

Questions about delete_resource_file

What does the delete_resource_file tool do? +

Delete a file from the Grail Resource Store by path (WRITE, destructive, Resource Store 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.

How do I enforce a policy on delete_resource_file? +

Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for delete_resource_file: 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.

What risk level is delete_resource_file? +

delete_resource_file is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_resource_file? +

Yes. Add a rate_limit block to the delete_resource_file 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.

How do I block delete_resource_file completely? +

Set action: deny in the PolicyLayer policy for delete_resource_file. 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.

What MCP server provides delete_resource_file? +

delete_resource_file 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.