Delete a file from the project by UUID. This permanently removes the file and all its methods/statements. WARNING: This is destructive and cannot be undone. Make sure the file is not referenced elsewhere before deleting.
Part of the Stellify server.
Free to start. No card required.
AI agents may call delete_file to permanently remove or destroy resources in Stellify. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call delete_file in a loop, permanently destroying resources in Stellify. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"delete_file"
]
}See the full Stellify policy for all 50 tools.
These attack patterns abuse exactly the kind of access delete_file gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Delete a file from the project by UUID. This permanently removes the file and all its methods/statements. WARNING: This is destructive and cannot be undone. Make sure the file is not referenced elsewhere before deleting.. It is categorised as a Destructive tool in the Stellify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stellify MCP server in PolicyLayer and add a rule for delete_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 Stellify. Nothing to install.
delete_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_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_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_file is provided by the Stellify MCP server (Stellify-Software-Ltd/stellify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 Stellify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.