【谨慎调用】直接删除文件，无需二次确认，操作不可逆！
AI agents call delete_file to permanently remove resources in LuzzyTool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes files without requiring confirmation or undo capability. It has the highest potential for unintended harm if an AI agent misuses it (e.g., deleting critical system or user files). While the warning label (【谨慎调用】means 'call with caution') shows awareness of risk, it does not change the fundamental destructive nature.
From the tool's definition Tool description states: '直接删除文件，无需二次确认，操作不可逆！' which translates to 'directly delete file, no second confirmation required, operation is irreversible!' The name 'delete_file' combined with the explicit warning about irreversibility and lack of confirmation…
Attacks that exploit this kind of access
【谨慎调用】直接删除文件，无需二次确认，操作不可逆！. It is categorised as a Destructive tool in the LuzzyTool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LuzzyTool 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 LuzzyTool. 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 LuzzyTool MCP server (luzzymeow/luzzytool). 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 →