build_brand_spot_from_mogrt_and_assets
Builds a branded ad assembly from real media assets, supports optional MOGRT overlay, and allows explicit clipPlan control. Default polish is optional so creative direction can come from LLM planning instead of hardcoded passes.
This record as markdown: /tools/adobe-premiere-pro-mcp/build-brand-spot-from-mogrt-and-assets.md
What build_brand_spot_from_mogrt_and_assets does on Adobe Premiere Pro
AI agents invoke build_brand_spot_from_mogrt_and_assets to trigger actions in Adobe Premiere Pro. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
clipPlan | array | — | Optional explicit edit plan. Reuses assemble_product_spot clipPlan semantics. |
mogrtPath | string | — | Optional absolute path to a .mogrt title or branding template |
assetPaths | array | Yes | Absolute paths to source assets in edit order |
motionStyle | string | — | Fallback motion style when clipPlan does not override it. Defaults to "alternate" in template mode. |
clipDuration | number | — | Default spacing in seconds for asset placement. Defaults to 4.0 |
sequenceName | string | Yes | Name for the new sequence |
titleStartTime | number | — | Timeline start time in seconds for the optional MOGRT. Defaults to 0.4 |
transitionName | string | — | Default transition when clipPlan does not override it. Defaults to "Cross Dissolve" in template mode. |
titleTrackIndex | number | — | Video track for the optional MOGRT overlay. Defaults to 1 |
videoTrackIndex | number | — | Base video track for the main assets. Defaults to 0 |
applyDefaultPolish | boolean | — | Whether to apply the legacy light polish pass (blur + small color tweak). Defaults to false. |
transitionDuration | number | — | Transition duration in seconds. Defaults to 0.5 |
Parameters from the server's own tool schema.
Why build_brand_spot_from_mogrt_and_assets is rated High
This tool orchestrates a complex workflow that automates video editing operations, media rendering, and asset compilation. While it produces reversible outputs (video edits that could be undone), the execution of automated composition logic, application of effects, and rendering processes classifies this as Execute rather than Write.
From the tool's definition Tool name and description indicate automated assembly of media into a branded ad spot—'builds a branded ad assembly from real media assets'—which triggers external operations (video composition, MOGRT application, asset integration) whose effects depend on…
Risk signalsHigh parameter count (41 properties)
Attacks that exploit this kind of access
The rule that runs build_brand_spot_from_mogrt_and_assets 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 build_brand_spot_from_mogrt_and_assets, this is the rule to start with:
build_brand_spot_from_mogrt_and_assets stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 build_brand_spot_from_mogrt_and_assets call is checked against it from then on.
Questions about build_brand_spot_from_mogrt_and_assets
Builds a branded ad assembly from real media assets, supports optional MOGRT overlay, and allows explicit clipPlan control. Default polish is optional so creative direction can come from LLM planning instead of hardcoded passes. It is categorised as a Execute tool in the Adobe Premiere Pro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_brand_spot_from_mogrt_and_assets accepts 12 parameters: clipPlan, mogrtPath, assetPaths, motionStyle, clipDuration, sequenceName, titleStartTime, transitionName, titleTrackIndex, videoTrackIndex, applyDefaultPolish, transitionDuration. Required: assetPaths, sequenceName. 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 build_brand_spot_from_mogrt_and_assets: 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.
build_brand_spot_from_mogrt_and_assets is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_brand_spot_from_mogrt_and_assets 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 build_brand_spot_from_mogrt_and_assets. 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.
build_brand_spot_from_mogrt_and_assets 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.
Across the catalogue