open_in_editor
Validate the current project and create a link that opens it in the Clipkit web editor, where the user can preview and refine it. This shares the PROJECT (nothing is rendered — that's render_video). Use after composing or editing. Returns a URL.
This record as markdown: /tools/dev-clipkit-clipkit/open-in-editor.md
What open_in_editor does on Clipkit
AI agents call open_in_editor to retrieve information from Clipkit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 open_in_editor is rated Low
The tool validates the current project state and constructs a shareable editor URL. It does not modify, delete, or execute anything; it reads/validates project data and returns a URL. The note 'nothing is rendered' confirms no side effects beyond URL generation.
From the tool's definition 'create a link that opens it in the Clipkit web editor' and 'Returns a URL' — the tool generates/returns a URL and validates the project, but does not modify or delete data
Attacks that exploit this kind of access
The rule that runs open_in_editor 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 open_in_editor, this is the rule to start with:
open_in_editor is read-only, so it stays allowed. 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 open_in_editor call is checked against it from then on.
Questions about open_in_editor
Validate the current project and create a link that opens it in the Clipkit web editor, where the user can preview and refine it. This shares the PROJECT (nothing is rendered — that's render_video). Use after composing or editing. Returns a URL. It is categorised as a Read tool in the Clipkit MCP Server, which means it retrieves data without modifying state.
open_in_editor accepts 1 parameter: project_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 open_in_editor: 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.
open_in_editor is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the open_in_editor 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 open_in_editor. 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.
open_in_editor 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