delete_file
Delete a file or directory on the API server.
This record as markdown: /tools/nyxstrike/delete-file.md
What delete_file does on Nyxstrike
AI agents call delete_file to permanently remove resources in Nyxstrike, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_file is rated Critical
This tool performs irreversible deletion of data (files/directories) on the server with no undo capability. Given the context of a penetration testing platform where an AI agent could be misused to delete critical system files, logs, or data without authorization, the blast radius is maximal. Destructive actions rank highest in severity hierarchy and warrant critical severity classification.
From the tool's definition Tool name is 'delete_file' with description 'Delete a file or directory on the API server.' The verb 'delete' combined with irreversible removal of files or directories directly matches the Destructive category definition.
Attacks that exploit this kind of access
The rule that runs delete_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_file, this is the rule to start with:
delete_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 Nyxstrike, apply this rule, and every delete_file call is checked against it from then on.
Questions about delete_file
Delete a file or directory on the API server. It is categorised as a Destructive tool in the Nyxstrike MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nyxstrike 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 Nyxstrike. 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 Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
Across the catalogue