fs_delete_file_with_approval
Delete a file (a backup is kept). Requires approval.
This record as markdown: /tools/yuga-hashimoto-localant/fs-delete-file-with-approval.md
What fs_delete_file_with_approval does on LocalAnt
AI agents call fs_delete_file_with_approval to permanently remove resources in LocalAnt, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why fs_delete_file_with_approval is rated Critical
This tool permanently removes files from the user's system. Although a backup copy is retained (mitigating factor that prevents 'critical' severity), the original file is deleted and cannot be recovered by normal means. This is an irreversible data loss operation that fits the Destructive category.
From the tool's definition Tool name explicitly contains 'delete_file' and description states 'Delete a file'. Despite the note that 'a backup is kept', the primary action is deletion, which is irreversible from the user's active filesystem perspective.
Attacks that exploit this kind of access
The rule that runs fs_delete_file_with_approval safely
PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fs_delete_file_with_approval, this is the rule to start with:
fs_delete_file_with_approval 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 LocalAnt, apply this rule, and every fs_delete_file_with_approval call is checked against it from then on.
Questions about fs_delete_file_with_approval
Delete a file (a backup is kept). Requires approval. It is categorised as a Destructive tool in the LocalAnt MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalAnt MCP server in PolicyLayer and add a rule for fs_delete_file_with_approval: 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 LocalAnt. Nothing to install.
fs_delete_file_with_approval 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 fs_delete_file_with_approval 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 fs_delete_file_with_approval. 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.
fs_delete_file_with_approval is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on LocalAnt, and thousands of servers like it.
Across the catalogue