# delete_file

Elimina un archivo Markdown de la bóveda.

Agent View of the PolicyLayer registry record for `delete_file`. HTML page: https://policylayer.com/tools/a2rg-obsidian-mcp/delete-file

## Facts

- Tool: `delete_file`
- Server: Obsidian (`@a2rg/obsidian-mcp`) — https://policylayer.com/tools/a2rg-obsidian-mcp.md
- Install: `npx -y @a2rg/obsidian-mcp`
- Homepage: https://www.npmjs.com/package/@a2rg/obsidian-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `path` | string | yes | Ruta relativa del archivo |

Parameters from the server's own tool schema.

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

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

## Why delete_file is rated Critical

An AI agent that decides to call delete_file doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Obsidian is gone. There is no undo for destructive operations.

Risk signals: Accepts file system path (path)

## Use case

AI agents call delete_file to permanently remove resources in Obsidian, 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 Obsidian:

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

## Other tools on Obsidian (7)

- `append_file` — Read — https://policylayer.com/tools/a2rg-obsidian-mcp/append-file.md
- `get_active_file` — Read — https://policylayer.com/tools/a2rg-obsidian-mcp/get-active-file.md
- `get_file` — Read — https://policylayer.com/tools/a2rg-obsidian-mcp/get-file.md
- `get_linked_notes` — Read — https://policylayer.com/tools/a2rg-obsidian-mcp/get-linked-notes.md
- `list_files` — Read — https://policylayer.com/tools/a2rg-obsidian-mcp/list-files.md
- `search_vault` — Read — https://policylayer.com/tools/a2rg-obsidian-mcp/search-vault.md
- `write_file` — Write — https://policylayer.com/tools/a2rg-obsidian-mcp/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=a2rg-obsidian-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a2rg-obsidian-mcp
