load_project
Import a previously shared project as the current project, by its share id or its editor URL (e.g. https://clipkit.dev/editor?id=…), returning its project_id. Use this to continue working on a project the user opened in the editor or shared earlier — the round-trip for open_in_editor. Pass an exi...
This record as markdown: /tools/dev-clipkit-clipkit/load-project.md
What load_project does on Clipkit
AI agents use load_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 |
|---|---|---|---|
id_or_url | string | Yes | A share id, or a clipkit.dev/editor?id=… URL. |
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 load_project is rated Medium
This tool creates or modifies state by importing a project and setting it as the current project, potentially overwriting an existing project if a project_id is provided. It is reversible (the original shared project remains intact), so it falls under Write rather than Destructive. The blast radius is medium since it could overwrite an existing project's state.
From the tool's definition 'Import a previously shared project as the current project' and 'Pass an existing project_id to load into that project; omit it to load into a new one'
Attacks that exploit this kind of access
The rule that runs load_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 load_project, this is the rule to start with:
load_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 load_project call is checked against it from then on.
Questions about load_project
Import a previously shared project as the current project, by its share id or its editor URL (e.g. https://clipkit.dev/editor?id=…), returning its project_id. Use this to continue working on a project the user opened in the editor or shared earlier — the round-trip for open_in_editor. Pass an existing project_id to load into that project; omit it to load into a new one. 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.
load_project accepts 2 parameters: id_or_url, project_id. Required: id_or_url. 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 load_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.
load_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 load_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 load_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.
load_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