import_folder
Imports all media files from a folder into the current Premiere Pro project.
This record as markdown: /tools/adobe-premiere-pro-mcp/import-folder.md
What import_folder does on Adobe Premiere Pro
AI agents use import_folder 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 |
|---|---|---|---|
binName | string | — | The name of the bin to import the media into |
recursive | boolean | — | Whether to import from subfolders recursively |
folderPath | string | Yes | The absolute path to the folder containing media files |
Parameters from the server's own tool schema.
Why import_folder is rated Medium
The import_folder tool adds media files to a Premiere Pro project, which is a write operation that creates new data structures within the project. While reversible (imported media can be removed), it modifies project state and could impact a large number of files if a folder contains many media items.
From the tool's definition Tool description states it 'Imports all media files from a folder into the current Premiere Pro project' — this creates new media elements in the project, modifying its state reversibly.
Attacks that exploit this kind of access
The rule that runs import_folder 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 import_folder, this is the rule to start with:
import_folder 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 import_folder call is checked against it from then on.
Questions about import_folder
Imports all media files from a folder into the current Premiere Pro project. 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.
import_folder accepts 3 parameters: binName, recursive, folderPath. Required: folderPath. 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 import_folder: 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.
import_folder 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 import_folder 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 import_folder. 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.
import_folder 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