save_project_as
Saves the current project with a new name and location.
This record as markdown: /tools/adobe-premiere-pro-mcp/save-project-as.md
What save_project_as does on Adobe Premiere Pro
AI agents use save_project_as 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 new name for the project |
location | string | Yes | The absolute directory path where the project should be saved |
Parameters from the server's own tool schema.
Why save_project_as is rated Medium
This tool creates a new project file or updates an existing one, which is a reversible write operation. While it modifies data persistence, it does not irreversibly delete data (so not Destructive), execute arbitrary code (so not Execute), or involve financial transactions (so not Financial).
From the tool's definition Tool name 'save_project_as' and description 'Saves the current project with a new name and location' indicate a write operation that creates or modifies data (the project file) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs save_project_as 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 save_project_as, this is the rule to start with:
save_project_as 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 save_project_as call is checked against it from then on.
Questions about save_project_as
Saves the current project with a new name and location. 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.
save_project_as 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 save_project_as: 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.
save_project_as 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 save_project_as 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 save_project_as. 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.
save_project_as 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