import_mogrt
Imports a Motion Graphics Template (.mogrt) file into a sequence.
This record as markdown: /tools/adobe-premiere-pro-mcp/import-mogrt.md
What import_mogrt does on Adobe Premiere Pro
AI agents use import_mogrt 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 |
|---|---|---|---|
time | number | Yes | The time in seconds where the MOGRT should be placed |
mogrtPath | string | Yes | The absolute path to the .mogrt file |
sequenceId | string | Yes | The ID of the sequence |
audioTrackIndex | number | — | The audio track index (default: 0) |
videoTrackIndex | number | — | The video track index (default: 0) |
Parameters from the server's own tool schema.
Why import_mogrt is rated Medium
This tool creates or modifies project content by adding a motion graphics template to a sequence. While it affects the editing project (reversible change), it does not execute arbitrary code, delete data, or move money. The capability to add templates to sequences is a content modification operation, making it Write-category.
From the tool's definition Tool imports a Motion Graphics Template (.mogrt) file into a sequence, which creates/adds new content to the project. The description explicitly indicates data creation/modification ('imports...into a sequence') without deletion or irreversible destruction.
Attacks that exploit this kind of access
The rule that runs import_mogrt 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_mogrt, this is the rule to start with:
import_mogrt 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_mogrt call is checked against it from then on.
Questions about import_mogrt
Imports a Motion Graphics Template (.mogrt) file into a sequence. 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_mogrt accepts 5 parameters: time, mogrtPath, sequenceId, audioTrackIndex, videoTrackIndex. Required: time, mogrtPath, sequenceId. 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_mogrt: 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_mogrt 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_mogrt 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_mogrt. 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_mogrt 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