add_element
Append a single element to an existing project — a TWEAK, e.g. dropping in one more caption or shape. By default it is added at the top level; pass parent_id to add it INTO a group (nested). The element is any valid schema element: video, image, text, shape, audio, group, caption, or particles. T...
This record as markdown: /tools/dev-clipkit-clipkit/add-element.md
What add_element does on Clipkit
AI agents use add_element to create or update resources in Clipkit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clipkit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
element | object | Yes | A Clipkit element object. Must include `type`. |
parent_id | string | — | Optional id of a group to add this element INTO (nested). Omit to add at the top level. |
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 add_element is rated Medium
This tool creates and adds new elements (video, image, text, shape, audio, group, caption, or particles) to an existing project structure. It modifies the project state reversibly through element insertion. While it affects project composition, the change is not destructive (elements can be removed) and does not execute arbitrary code or trigger external operations.
From the tool's definition Tool description states it will "Append a single element to an existing project" and "The new element is validated as part of the project as a whole before being added." This is a create/modify operation on project data.
Attacks that exploit this kind of access
The rule that runs add_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 add_element, this is the rule to start with:
add_element stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Clipkit, apply this rule, and every add_element call is checked against it from then on.
Questions about add_element
Append a single element to an existing project — a TWEAK, e.g. dropping in one more caption or shape. By default it is added at the top level; pass parent_id to add it INTO a group (nested). The element is any valid schema element: video, image, text, shape, audio, group, caption, or particles. To create a composition or add several elements at once, build the JSON and use set_project instead. The new element is validated as part of the project as a whole before being added. Call get_schema(element_type) for the exact per-type fields; unrecognized keys are flagged. It is categorised as a Write tool in the Clipkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_element accepts 3 parameters: element, parent_id, project_id. Required: element. 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 add_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.
add_element is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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.
This server
Across the catalogue