speed_change
Changes the playback speed of a clip.
This record as markdown: /tools/adobe-premiere-pro-mcp/speed-change.md
What speed_change does on Adobe Premiere Pro
AI agents use speed_change 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 |
|---|---|---|---|
speed | number | Yes | Speed multiplier (0.1 = 10% speed, 2.0 = 200% speed) |
clipId | string | Yes | The ID of the clip |
maintainAudio | boolean | — | Whether to maintain audio pitch when changing speed |
Parameters from the server's own tool schema.
Why speed_change is rated Medium
Speed changes in video editing are reversible modifications to clip properties. While this affects the final output and timeline composition, the change can be undone (undo/redo in Premiere Pro). The severity is medium because misuse could degrade video quality or create unexpected playback artifacts that would require correction, but the effects are not permanent and can be easily reverted.
From the tool's definition The tool 'speed_change' modifies a clip's playback speed property in Adobe Premiere Pro, which alters the clip's characteristics in a reversible manner.
Attacks that exploit this kind of access
The rule that runs speed_change 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 speed_change, this is the rule to start with:
speed_change 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 speed_change call is checked against it from then on.
Questions about speed_change
Changes the playback speed of a clip. 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.
speed_change accepts 3 parameters: speed, clipId, maintainAudio. Required: speed, clipId. 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 speed_change: 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.
speed_change 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 speed_change 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 speed_change. 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.
speed_change 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