# seafile_delete

A destructive tool on the Seafile MCP Server MCP server.

Agent View of the PolicyLayer registry record for `seafile_delete`. HTML page: https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-delete

## Facts

- Tool: `seafile_delete`
- Server: Seafile MCP Server (`5p00kyy/seafile-mcp`) — https://policylayer.com/tools/5p00kyy-seafile-mcp.md
- Homepage: https://github.com/5p00kyy/seafile-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "seafile_delete",
    "arguments": {}
  }
}
```

## Why seafile_delete is rated Critical

The tool name explicitly indicates deletion functionality in a storage management context. Deletion is irreversible—files cannot be recovered through normal operations. This represents a high blast radius if invoked by an AI agent on unintended targets (wrong files, directories, or libraries).

From the tool's own definition: "Tool name is 'seafile_delete' with no description provided. In the context of a cloud storage system (Seafile), 'delete' operations irreversibly remove files or directories."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Seafile MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "seafile_delete"
  ]
}
```

## Other tools on Seafile MCP Server (13)

- `seafile_get_download_link` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-get-download-link.md
- `seafile_get_file_info` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-get-file-info.md
- `seafile_get_library_info` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-get-library-info.md
- `seafile_list_directory` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-list-directory.md
- `seafile_list_libraries` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-list-libraries.md
- `seafile_read_file` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-read-file.md
- `seafile_search` — Read — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-search.md
- `seafile_copy` — Write — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-copy.md
- `seafile_create_directory` — Write — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-create-directory.md
- `seafile_move` — Write — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-move.md
- `seafile_rename` — Write — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-rename.md
- `seafile_upload_file` — Write — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-upload-file.md
- `seafile_write_file` — Write — https://policylayer.com/tools/5p00kyy-seafile-mcp/seafile-write-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=5p00kyy-seafile-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/5p00kyy-seafile-mcp