add_audio_keyframes
Adds keyframes to audio levels for dynamic volume changes.
This record as markdown: /tools/adobe-premiere-pro-mcp/add-audio-keyframes.md
What add_audio_keyframes does on Adobe Premiere Pro
AI agents use add_audio_keyframes 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 |
|---|---|---|---|
clipId | string | Yes | The ID of the audio clip |
keyframes | array | Yes | Array of keyframe data |
Parameters from the server's own tool schema.
Why add_audio_keyframes is rated Medium
This tool creates new keyframe objects that modify audio parameter data within a video project. While it changes the project state, these modifications are reversible (keyframes can be deleted or adjusted). It does not execute arbitrary code, delete content irreversibly, or move financial resources. It falls under Write because it creates or modifies project data reversibly.
From the tool's definition Tool name 'add_audio_keyframes' and description 'Adds keyframes to audio levels for dynamic volume changes' indicate creating/modifying keyframe data in Adobe Premiere Pro's audio timeline.
Attacks that exploit this kind of access
The rule that runs add_audio_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 add_audio_keyframes, this is the rule to start with:
add_audio_keyframes 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_audio_keyframes call is checked against it from then on.
Questions about add_audio_keyframes
Adds keyframes to audio levels for dynamic volume changes. 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_audio_keyframes accepts 2 parameters: clipId, keyframes. Required: clipId, keyframes. 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_audio_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.
add_audio_keyframes 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_audio_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 add_audio_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.
add_audio_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