add_keyframe
Adds a keyframe to a clip component parameter at a specific time.
This record as markdown: /tools/adobe-premiere-pro-mcp/add-keyframe.md
What add_keyframe does on Adobe Premiere Pro
AI agents use add_keyframe to create or update resources in Adobe Premiere Pro, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Premiere Pro environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
time | number | Yes | The time in seconds for the keyframe |
value | number | Yes | The value to set at this keyframe |
clipId | string | Yes | The ID of the clip |
paramName | string | Yes | The display name of the parameter (e.g., "Position", "Scale") |
componentName | string | Yes | The display name of the component (e.g., "Motion", "Opacity") |
Parameters from the server's own tool schema.
Why add_keyframe is rated Medium
The tool creates or modifies project data (keyframes) within Adobe Premiere Pro in a way that can be undone. This fits the Write category: creates new data structures reversibly. It does not execute external code (Execute), permanently delete data (Destructive), or move financial assets (Financial).
From the tool's definition Tool description states 'Adds a keyframe to a clip component parameter at a specific time.' The verb 'Adds' indicates creation of new data (keyframe metadata). This is a reversible modification to a video project.
Attacks that exploit this kind of access
The rule that runs add_keyframe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adobe Premiere Pro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_keyframe, this is the rule to start with:
add_keyframe 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 Adobe Premiere Pro, apply this rule, and every add_keyframe call is checked against it from then on.
Questions about add_keyframe
Adds a keyframe to a clip component parameter at a specific time. It is categorised as a Write tool in the Adobe Premiere Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_keyframe accepts 5 parameters: time, value, clipId, paramName, componentName. Required: time, value, clipId, paramName, componentName. The full parameter table on this page comes from the server's own tool schema.
Register the Adobe Premiere Pro MCP server in PolicyLayer and add a rule for add_keyframe: 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 Adobe Premiere Pro. Nothing to install.
add_keyframe 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_keyframe 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_keyframe. 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_keyframe is provided by the Adobe Premiere Pro MCP server (adobe-premiere-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Premiere Pro, and thousands of servers like it.
This server
Across the catalogue