create_project
Creates a new Adobe Premiere Pro project. Use this when the user wants to start a new video editing project from scratch.
This record as markdown: /tools/adobe-premiere-pro-mcp/create-project.md
What create_project does on Adobe Premiere Pro
AI agents use create_project 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 |
|---|---|---|---|
name | string | Yes | The name for the new project, e.g., "My Summer Vacation" |
location | string | Yes | The absolute directory path where the project file should be saved, e.g., "/Users/user/Documents/Videos" |
Parameters from the server's own tool schema.
Why create_project is rated Medium
Creating a new project is a reversible write operation—the project can be deleted or discarded. It does not execute arbitrary code, delete existing data irreversibly, or move money. While it initiates a new file/state, this is a standard Write category action.
From the tool's definition Tool description states it 'Creates a new Adobe Premiere Pro project', which is a create operation that modifies the filesystem and application state by instantiating a new project file.
Attacks that exploit this kind of access
The rule that runs create_project 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 create_project, this is the rule to start with:
create_project 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 create_project call is checked against it from then on.
Questions about create_project
Creates a new Adobe Premiere Pro project. Use this when the user wants to start a new video editing project from scratch. 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.
create_project accepts 2 parameters: name, location. Required: name, location. 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 create_project: 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.
create_project 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 create_project 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 create_project. 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.
create_project 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