rename_project_item
Renames a project item (sequence, bin, clip) by setting its name. Use this when duplicate_sequence does not propagate the new name to the project panel.
This record as markdown: /tools/adobe-premiere-pro-mcp/rename-project-item.md
What rename_project_item does on Adobe Premiere Pro
AI agents use rename_project_item 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 |
|---|---|---|---|
newName | string | Yes | The new name for the project item |
projectItemId | string | Yes | The ID of the project item to rename |
Parameters from the server's own tool schema.
Why rename_project_item is rated Medium
This tool modifies project metadata (the name property of a sequence, bin, or clip) without deleting data or causing irreversible changes. The effect can be undone by renaming again. It does not execute code, delete anything, or involve financial operations.
From the tool's definition The tool description states it 'Renames a project item' by 'setting its name'. Renaming is a reversible metadata modification operation.
Attacks that exploit this kind of access
The rule that runs rename_project_item 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 rename_project_item, this is the rule to start with:
rename_project_item 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 rename_project_item call is checked against it from then on.
Questions about rename_project_item
Renames a project item (sequence, bin, clip) by setting its name. Use this when duplicate_sequence does not propagate the new name to the project panel. 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.
rename_project_item accepts 2 parameters: newName, projectItemId. Required: newName, projectItemId. 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 rename_project_item: 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.
rename_project_item 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 rename_project_item 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 rename_project_item. 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.
rename_project_item 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