# delete_element

Delete the element with the given id, anywhere in the tree (including one nested inside a group or its mask) — a tweak to an existing composition. (The project must keep at least one top-level element.)

Agent View of the PolicyLayer registry record for `delete_element`. HTML page: https://policylayer.com/tools/dev-clipkit-clipkit/delete-element

## Facts

- Tool: `delete_element`
- Server: Clipkit (`https://www.clipkit.dev/mcp`) — https://policylayer.com/tools/dev-clipkit-clipkit.md
- Homepage: https://github.com/clipkit-video/clipkit
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The id of the element to delete. |
| `project_id` | string | no | Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project. |

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_element",
    "arguments": {
      "id": "<id>"
    }
  }
}
```

## Why delete_element is rated Critical

The tool permanently removes an element from a composition tree. Although constrained by the requirement that 'the project must keep at least one top-level element', the action cannot be undone and data is lost. This qualifies as Destructive rather than Write. Severity is high because an AI agent could delete significant portions of a user's design work, though the constraint mitigates total project destruction.

From the tool's own definition: "Tool name is 'delete_element' and description explicitly states 'Delete the element with the given id' — this is an irreversible deletion operation."

## Use case

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

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

## Other tools on Clipkit (14)

- `describe_project` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/describe-project.md
- `get_project` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/get-project.md
- `get_schema` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/get-schema.md
- `open_in_editor` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/open-in-editor.md
- `preview_still` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/preview-still.md
- `read_docs` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/read-docs.md
- `validate_project` — Read — https://policylayer.com/tools/dev-clipkit-clipkit/validate-project.md
- `add_element` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/add-element.md
- `create_project` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/create-project.md
- `create_promo` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/create-promo.md
- `edit_element` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/edit-element.md
- `ingest_asset` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/ingest-asset.md
- `load_project` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/load-project.md
- `set_project` — Write — https://policylayer.com/tools/dev-clipkit-clipkit/set-project.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=dev-clipkit-clipkit · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-clipkit-clipkit