get_keyframes
Gets all keyframes for a clip component parameter.
This record as markdown: /tools/adobe-premiere-pro-mcp/get-keyframes.md
What get_keyframes does on Adobe Premiere Pro
AI agents call get_keyframes to retrieve information from Adobe Premiere Pro 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 |
|---|---|---|---|
clipId | string | Yes | The ID of the clip |
paramName | string | Yes | The display name of the parameter |
componentName | string | Yes | The display name of the component |
Parameters from the server's own tool schema.
Why get_keyframes is rated Low
This tool retrieves keyframe data from a clip parameter without creating, modifying, or deleting any information. It is a query operation that has no side effects on the Premiere Pro project state, making it a Read operation with minimal risk.
From the tool's definition Tool name 'get_keyframes' and description 'Gets all keyframes for a clip component parameter' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs get_keyframes 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 get_keyframes, this is the rule to start with:
get_keyframes 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 Adobe Premiere Pro, apply this rule, and every get_keyframes call is checked against it from then on.
Questions about get_keyframes
Gets all keyframes for a clip component parameter. It is categorised as a Read tool in the Adobe Premiere Pro MCP Server, which means it retrieves data without modifying state.
get_keyframes accepts 3 parameters: clipId, paramName, componentName. Required: 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 get_keyframes: 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.
get_keyframes 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 get_keyframes 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 get_keyframes. 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.
get_keyframes 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