Delete a file from the workspace folder
AI agents call delete_file to permanently remove resources in Node Dev MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a file cannot be undone without a backup or version control recovery. This is a destructive operation that permanently removes data from the user's workspace. While the blast radius is somewhat contained to local development files (not production systems or financial data), accidental or malicious deletion of critical source code, configuration files, or build artifacts could cause significant harm.
From the tool's definition Tool name is 'delete_file' and description states 'Delete a file from the workspace folder'—this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a file from the workspace folder. It is categorised as a Destructive tool in the Node Dev MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Node Dev MCP Server 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 Node Dev MCP Server. 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 Node Dev MCP Server MCP server (liamcarver/node-dev-mcp-server). 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 →