# delete_path

Delete a file or directory within the project.

Agent View of the PolicyLayer registry record for `delete_path`. HTML page: https://policylayer.com/tools/54yyyu-code-mcp/delete-path

## Facts

- Tool: `delete_path`
- Server: Code (`54yyyu/code-mcp`) — https://policylayer.com/tools/54yyyu-code-mcp.md
- Homepage: https://github.com/54yyyu/code-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, 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": "delete_path",
    "arguments": {}
  }
}
```

## Why delete_path is rated Critical

This tool permanently removes data without reversibility or undo capability. While the blast radius is limited to the project directory scope, accidental or malicious deletion of critical project files (source code, configuration, documentation) would be severely damaging. This is the canonical Destructive category case.

From the tool's own definition: "Tool name 'delete_path' combined with description 'Delete a file or directory within the project' explicitly indicates irreversible deletion of files or directories."

## Use case

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

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

## Other tools on Code (8)

- `git_operation` — Execute — https://policylayer.com/tools/54yyyu-code-mcp/git-operation.md
- `run_command` — Execute — https://policylayer.com/tools/54yyyu-code-mcp/run-command.md
- `list_directory` — Read — https://policylayer.com/tools/54yyyu-code-mcp/list-directory.md
- `read_file` — Read — https://policylayer.com/tools/54yyyu-code-mcp/read-file.md
- `create_directory` — Write — https://policylayer.com/tools/54yyyu-code-mcp/create-directory.md
- `edit_block` — Write — https://policylayer.com/tools/54yyyu-code-mcp/edit-block.md
- `edit_file` — Write — https://policylayer.com/tools/54yyyu-code-mcp/edit-file.md
- `smart_edit` — Write — https://policylayer.com/tools/54yyyu-code-mcp/smart-edit.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=54yyyu-code-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/54yyyu-code-mcp