set_metadata
Sets a project metadata value on a project item.
This record as markdown: /tools/adobe-premiere-pro-mcp/set-metadata.md
What set_metadata does on Adobe Premiere Pro
AI agents use set_metadata 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 |
|---|---|---|---|
key | string | Yes | The metadata key/field name |
value | string | Yes | The metadata value to set |
projectItemId | string | Yes | The ID of the project item |
Parameters from the server's own tool schema.
Why set_metadata is rated Medium
This tool creates or modifies metadata on Premiere Pro project items. While metadata changes are typically reversible and have limited blast radius compared to destructive operations (like deleting clips), they still constitute write operations that alter project state.
From the tool's definition Tool name 'set_metadata' and description 'Sets a project metadata value on a project item' indicate modification of project data.
Attacks that exploit this kind of access
The rule that runs set_metadata 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 set_metadata, this is the rule to start with:
set_metadata 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 set_metadata call is checked against it from then on.
Questions about set_metadata
Sets a project metadata value on a project item. 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.
set_metadata accepts 3 parameters: key, value, projectItemId. Required: key, value, projectItemId. 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 set_metadata: 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.
set_metadata 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 set_metadata 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 set_metadata. 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.
set_metadata 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