set_project
Replace the entire project with the given source JSON, returning its project_id. This is the PRIMARY way to build: use it to create a composition or to add/change many elements at once. (To tweak a single element in an existing project, use edit_element / add_element / delete_element instead.) Pa...
This record as markdown: /tools/dev-clipkit-clipkit/set-project.md
What set_project does on Clipkit
AI agents use set_project 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 |
|---|---|---|---|
source | object | Yes | A full Clipkit source object. |
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 set_project is rated Medium
This tool creates or modifies data reversibly: it can replace an entire project (Write) or create a new one. While the description is cut off, the confirmed capability to 'Replace the entire project' and 'add/change many elements at once' clearly indicates data modification.
From the tool's definition Tool description states 'Replace the entire project with the given source JSON' and 'use it to create a composition or to add/change many elements at once.' Key verbs: 'Replace' and 'add/change'.
Attacks that exploit this kind of access
The rule that runs set_project 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 set_project, this is the rule to start with:
set_project 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 set_project call is checked against it from then on.
Questions about set_project
Replace the entire project with the given source JSON, returning its project_id. This is the PRIMARY way to build: use it to create a composition or to add/change many elements at once. (To tweak a single element in an existing project, use edit_element / add_element / delete_element instead.) Pass an existing project_id to replace that project; omit it to create a new one (note the returned id). The input is validated against the @clipkit/protocol before being accepted; invalid inputs return an error. Shape: { width, height, duration, frame_rate, output_format, background_color?, fonts?, camera?, lights?, elements:[…] }; every element has a type plus base fields (id, x, y, width, height, time, duration, track, opacity, rotation, animations, keyframe_animations) and type-specific fields. For exact field names + types call get_schema (optionally with an element_type) — the runtime ignores unrecognized keys, and this tool flags any it does not recognize. 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.
set_project accepts 2 parameters: source, project_id. Required: source. 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 set_project: 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.
set_project 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 set_project 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 set_project. 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.
set_project 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