# 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. Agent View of the PolicyLayer registry record for `build_brand_spot_from_mogrt_and_assets`. HTML page: https://policylayer.com/tools/adobe-premiere-pro-mcp/build-brand-spot-from-mogrt-and-assets ## Facts - Tool: `build_brand_spot_from_mogrt_and_assets` - Server: Adobe Premiere Pro (`adobe-premiere-pro-mcp`) — https://policylayer.com/tools/adobe-premiere-pro-mcp.md - Install: `npx -y adobe-premiere-pro-mcp` - Homepage: https://www.npmjs.com/package/adobe-premiere-pro-mcp - Risk category: Execute (High risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 12 (2 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `clipPlan` | array | no | Optional explicit edit plan. Reuses assemble_product_spot clipPlan semantics. | | `mogrtPath` | string | no | Optional absolute path to a .mogrt title or branding template | | `assetPaths` | array | yes | Absolute paths to source assets in edit order | | `motionStyle` | string | no | Fallback motion style when clipPlan does not override it. Defaults to "alternate" in template mode. | | `clipDuration` | number | no | Default spacing in seconds for asset placement. Defaults to 4.0 | | `sequenceName` | string | yes | Name for the new sequence | | `titleStartTime` | number | no | Timeline start time in seconds for the optional MOGRT. Defaults to 0.4 | | `transitionName` | string | no | Default transition when clipPlan does not override it. Defaults to "Cross Dissolve" in template mode. | | `titleTrackIndex` | number | no | Video track for the optional MOGRT overlay. Defaults to 1 | | `videoTrackIndex` | number | no | Base video track for the main assets. Defaults to 0 | | `applyDefaultPolish` | boolean | no | Whether to apply the legacy light polish pass (blur + small color tweak). Defaults to false. | | `transitionDuration` | number | no | Transition duration in seconds. Defaults to 0.5 | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "build_brand_spot_from_mogrt_and_assets", "arguments": { "assetPaths": [], "sequenceName": "" } } } ``` ## 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 own 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 signals: High parameter count (41 properties) ## Use case 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. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adobe Premiere Pro: ```json { "version": "1", "default": "deny", "tools": { "build_brand_spot_from_mogrt_and_assets": { "limits": [ { "counter": "build_brand_spot_from_mogrt_and_assets_rate", "window": "minute", "max": 10, "scope": "grant" } ] } } } ``` ## Other tools on Adobe Premiere Pro (282) - `clear_item_in_out` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/clear-item-in-out.md - `clear_sequence_in_out` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/clear-sequence-in-out.md - `delete_bin` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-bin.md - `delete_marker` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-marker.md - `delete_multiple_project_items` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-multiple-project-items.md - `delete_preview_files` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-preview-files.md - `delete_project_item` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-project-item.md - `delete_sequence` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-sequence.md - `delete_track` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/delete-track.md - `remove_all_effects` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-all-effects.md - `remove_effect` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-effect.md - `remove_effect_by_name` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-effect-by-name.md - `remove_from_timeline` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-from-timeline.md - `remove_keyframe` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-keyframe.md - `remove_keyframe_range` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-keyframe-range.md - `remove_selected_clips` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/remove-selected-clips.md - `ripple_delete` — Destructive — https://policylayer.com/tools/adobe-premiere-pro-mcp/ripple-delete.md - `add_to_render_queue` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/add-to-render-queue.md - `auto_reframe_sequence` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/auto-reframe-sequence.md - `build_motion_graphics_demo` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/build-motion-graphics-demo.md - `execute_extendscript` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/execute-extendscript.md - `export_sequence` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/export-sequence.md - `open_project` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/open-project.md - `set_playhead_position` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/set-playhead-position.md - `start_batch_encode` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/start-batch-encode.md - `stop_playback` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/stop-playback.md - `undo` — Execute — https://policylayer.com/tools/adobe-premiere-pro-mcp/undo.md - `consolidate_and_transfer` — Financial — https://policylayer.com/tools/adobe-premiere-pro-mcp/consolidate-and-transfer.md - `check_offline_media` — Read — https://policylayer.com/tools/adobe-premiere-pro-mcp/check-offline-media.md - `detect_silence` — Read — https://policylayer.com/tools/adobe-premiere-pro-mcp/detect-silence.md - …and 252 more: https://policylayer.com/tools/adobe-premiere-pro-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adobe-premiere-pro-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adobe-premiere-pro-mcp