Shell MCP

deleteFile

Permanently deletes a single file from the filesystem. Returns confirmation on success; throws error for non-existent files or blocked system paths.

Instructions

Permanently delete a single file from the filesystem. This operation is irreversible. Only regular files can be deleted — use the exec tool with rmdir for directories. Returns a confirmation message on success. Throws an error if the file does not exist. Paths targeting sensitive system directories (e.g. /etc/shadow, /proc/, /dev/) are blocked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "deleteFile"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute or relative path to the file to delete. Relative paths are resolved from the server's working directory. Must not be empty or contain null bytes. Example: `/tmp/temp-file.txt`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 29, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully covers behavioral traits: irreversible operation, returns confirmation, throws error on nonexistent file, and blocks sensitive paths. This exceeds expectations for a simple delete tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five concise sentences front-load the main action and add critical details (irreversibility, error behavior, blocked paths) without redundancy. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having only one parameter, no output schema, and no annotations, the description comprehensively covers purpose, usage, behaviors, errors, and security restrictions. It leaves no gaps for an AI agent to misunderstand.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (path) with full schema coverage (100%). The schema already describes constraints and examples. The description adds context about path resolution and blocked paths, but does not augment the parameter meaning beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it permanently deletes a single file from the filesystem. It specifies it's irreversible and only for regular files, distinguishing it from the sibling `exec` tool for directory removal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (delete regular file) and when not to (use `exec` with rmdir for directories). Also warns about blocked sensitive system directories, providing clear context for safe usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server