fs_delete

A destructive tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54rt1n-container-mcp/fs-delete.md

WHAT IT DOES

What fs_delete does on Container-MCP

AI agents call fs_delete to permanently remove resources in Container-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why fs_delete is rated Critical

File deletion is an irreversible operation that destroys data without possibility of recovery (absent external backups). Even in a sandboxed container environment, this represents a significant risk if an AI agent misuses it to delete critical files, configurations, or data. This exceeds Execute category because the action cannot be undone, making it Destructive.

From the tool's definition Tool name 'fs_delete' combined with sibling tools (fs_apply_diff, fs_list, fs_move, fs_read, fs_write) indicates file system operations. The 'delete' operation irreversibly removes files.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fs_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Container-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fs_delete, this is the rule to start with:

fs_delete Hidden

fs_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Container-MCP, apply this rule, and every fs_delete call is checked against it from then on.

FAQ

Questions about fs_delete

What does the fs_delete tool do? +

fs_delete is a destructive tool on the Container MCP server. It is categorised as a Destructive tool in the Container-MCP 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 fs_delete? +

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

What risk level is fs_delete? +

fs_delete 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 fs_delete? +

Yes. Add a rate_limit block to the fs_delete 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 fs_delete completely? +

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

fs_delete is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Container, and thousands of servers like it.

This server

All 27 Container tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →