DELETE a single file. Refuses directories (no recursive delete). Path must validate.
AI agents call delete_file to permanently remove resources in Nexus Core — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool directly deletes files with no undo mechanism. Although it refuses directories (limiting blast radius to single files), deletion is irreversible and meets the definition of Destructive. In the context of a personal assistant, misuse could result in loss of critical user data. Severity is high rather than critical because it is scoped to individual files and requires valid path specification.
From the tool's definition DELETE a single file. Path must validate.
Attacks that exploit this kind of access
DELETE a single file. Refuses directories (no recursive delete). Path must validate. It is categorised as a Destructive tool in the Nexus Core MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nexus Core 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 Nexus Core. 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 Nexus Core MCP server (noumenon-ai/nexus-core). 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 →