delete_app_file
Delete a file from a multi-file FlowDot app. Permanently removes the file from the app. This action cannot be undone. Note: Deleting the entry point file will require you to set a new entry point using set_app_entry_file.
This record as markdown: /tools/flowdot-llc-mcp-server/delete-app-file.md
What delete_app_file does on FlowDot MCP Server
AI agents call delete_app_file to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_app_file is rated Critical
This tool irreversibly deletes data (app files) with no undo mechanism. Deletion is the canonical destructive operation. While the blast radius is scoped to a single app's files (not system-wide deletion), the permanent and unreversible nature of file deletion from a multi-file app, combined with potential cascading effects (requiring entry point reassignment if the entry file is deleted), justifies 'high' severity.
From the tool's definition Tool description explicitly states: 'Permanently removes the file from the app. This action cannot be undone.' The name contains 'delete' and the description confirms irreversible deletion of app files.
Attacks that exploit this kind of access
The rule that runs delete_app_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_app_file, this is the rule to start with:
delete_app_file is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every delete_app_file call is checked against it from then on.
Questions about delete_app_file
Delete a file from a multi-file FlowDot app. Permanently removes the file from the app. This action cannot be undone. Note: Deleting the entry point file will require you to set a new entry point using set_app_entry_file. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_app_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 FlowDot MCP Server. Nothing to install.
delete_app_file 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_app_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.
Set action: deny in the PolicyLayer policy for delete_app_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.
delete_app_file is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
Across the catalogue