File Deletion

1 tools. 1 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

1 can modify or destroy data
0 read-only
1 tools total
Read (0) Write / Execute (0) Destructive / Financial (1)

Destructive tools (delete_file) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Deny destructive operations
delete_file:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

DESTRUCTIVE 1 tools
Can an AI agent delete data through the File Deletion MCP server? +

Yes. The File Deletion server exposes 1 destructive tools including delete_file. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How many tools does the File Deletion MCP server expose? +

1 tools across 1 categories: Destructive. 0 are read-only. 1 can modify, create, or delete data.

How do I add Intercept to my File Deletion setup? +

One line change. Instead of running the File Deletion server directly, prefix it with Intercept: intercept -c qpd-v-mcp-delete.yaml -- npx -y @qpd-v/mcp-delete. Download a pre-built policy from policylayer.com/policies/qpd-v-mcp-delete and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.