edit_element

SERVERClipkit SOURCEhttps://www.clipkit.dev/mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-clipkit-clipkit/edit-element.md

WHAT IT DOES

What edit_element does on Clipkit

AI agents use edit_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
`id`	string	Yes	The id of the element to edit.
`patch`	object	Yes	Partial element: the fields to change. Omitted keys are left as-is; a key set to null is removed.
`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.

RISK

Why edit_element is rated Medium

This tool modifies composition/project data by updating element properties. While it can remove fields (via null), it does not permanently delete elements or entire compositions—changes are reversible and the operation re-validates before acceptance.

From the tool's definition Tool description explicitly states it can 'Change fields on the element' and 'set a key to null to remove it', indicating modification of existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs edit_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 edit_element, this is the rule to start with:

edit_element Rate-limited

edit_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_element": {
      "limits": [
        {
          "counter": "edit_element_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Clipkit, apply this rule, and every edit_element call is checked against it from then on.

FAQ

Questions about edit_element

What does the edit_element tool do? +

Change fields on the element with the given id by merging in a partial element — only the keys you include change. The id may be any element ANYWHERE in the tree, including one nested inside a group (or its mask). Pass a whole nested value (e.g. a new keyframe_animations array) to replace that key; set a key to null to remove it. This is for TWEAKING an existing composition. To create a composition or change many elements at once, edit the JSON and call set_project instead. The result is re-validated before being accepted. 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.

What parameters does edit_element accept? +

edit_element accepts 3 parameters: id, patch, project_id. Required: id, patch. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on edit_element? +

Register the Clipkit MCP server in PolicyLayer and add a rule for edit_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.

What risk level is edit_element? +

edit_element is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit edit_element? +

Yes. Add a rate_limit block to the edit_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.

How do I block edit_element completely? +

Set action: deny in the PolicyLayer policy for edit_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.

What MCP server provides edit_element? +

edit_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.

KEEP EXPLORING

More on Clipkit, and thousands of servers like it.

This server

All 15 Clipkit tools →

Across the catalogue

edit_screen on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →