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.)
This record as markdown: /tools/dev-clipkit-clipkit/delete-element.md
What delete_element does on Clipkit
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The id of the element to delete. |
project_id | string | — | 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.
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 definition Tool name is 'delete_element' and description explicitly states 'Delete the element with the given id' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Clipkit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_element, this is the rule to start with:
delete_element is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Clipkit, apply this rule, and every delete_element call is checked against it from then on.
Questions about 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.). It is categorised as a Destructive tool in the Clipkit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_element accepts 2 parameters: id, project_id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Clipkit MCP server in PolicyLayer and add a rule for delete_element: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Clipkit. Nothing to install.
delete_element is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_element rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for delete_element. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
delete_element is provided by the Clipkit MCP server (https://www.clipkit.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Clipkit, and thousands of servers like it.
Across the catalogue