add_clip_effect
AI agents use add_clip_effect to create or update resources in Media-Editor-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Media-Editor-MCP environment.
The tool creates or modifies video editing elements (effects on clips) reversibly within a draft project. This is consistent with Write category—changes can be undone in the editor. Severity is medium because misuse could corrupt or deface a project, but effects are applied to individual clips and are not destructive or financial.
From the tool's definition Tool name 'add_clip_effect' indicates modification of video clip properties. Description is empty, limiting precision. Sibling tools like 'add_animation', 'add_filter', 'add_audio', 'add_text' all perform reversible modifications to media drafts.
Attacks that exploit this kind of access
add_clip_effect. It is categorised as a Write tool in the Media-Editor-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Media-Editor- MCP server in PolicyLayer and add a rule for add_clip_effect: 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 Media-Editor-MCP. Nothing to install.
add_clip_effect 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_clip_effect 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_clip_effect. 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_clip_effect is provided by the Media-Editor- MCP server (nguyenph88/media-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →