batch_delete_files

THE RISK

Critical Risk

Why batch_delete_files needs a policy

This tool permanently and irreversibly deletes data. The batch and parallel nature amplifies the blast radius—an AI agent with misaligned objectives or faulty reasoning could delete critical system files, user data, or entire directories in one operation, causing severe business continuity loss. This is the most destructive operation possible on a file system. Destructive is more severe than Execute or Write.

From the tool's definition Tool name 'batch_delete_files' with description 'Delete multiple files in parallel.' The verb 'delete' with the plural 'files' and parallel execution capability indicates irreversible removal of data at scale.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access batch_delete_files gives an agent:

POLICY

How to control batch_delete_files

PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_delete_files:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "batch_delete_files"
  ]
}

batch_delete_files disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register OODA Computer Control — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OODA Computer Control tools

Destructive clear_old_logs Delete audit log entries older than specified days. Use dryRun=true to preview. Destructive clipboard_clear Clear the clipboard. Destructive crud_batch_delete Delete multiple records in parallel. Destructive crud_delete Delete a record Destructive delete_file Delete a file or directory. For multiple deletions, use batch_delete_files. Destructive reset_config Reset configuration to defaults. Optionally specify a section to reset only that section. Destructive kill_process Kill a process by PID or name. Destructive close_window Close a window. Use force to kill the process.

All 99 OODA Computer Control tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in OODA Computer Control → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about batch_delete_files

What does the batch_delete_files tool do? +

Delete multiple files in parallel. It is categorised as a Destructive tool in the OODA Computer Control MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on batch_delete_files? +

Register the OODA Computer Control MCP server in PolicyLayer and add a rule for batch_delete_files: 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 OODA Computer Control. Nothing to install.

What risk level is batch_delete_files? +

batch_delete_files is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit batch_delete_files? +

Yes. Add a rate_limit block to the batch_delete_files 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.

How do I block batch_delete_files completely? +

Set action: deny in the PolicyLayer policy for batch_delete_files. 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.

What MCP server provides batch_delete_files? +

batch_delete_files is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OODA Computer Control tool call.

Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →