get_metadata
Gets project metadata and XMP metadata for a project item.
This record as markdown: /tools/adobe-premiere-pro-mcp/get-metadata.md
What get_metadata does on Adobe Premiere Pro
AI agents call get_metadata to retrieve information from Adobe Premiere Pro without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectItemId | string | Yes | The ID of the project item |
Parameters from the server's own tool schema.
Why get_metadata is rated Low
This tool performs a read-only query operation on metadata within an Adobe Premiere Pro project. It retrieves information about a project item without creating, modifying, deleting, or executing any actions. The operation has no side effects and presents minimal risk of misuse by an AI agent, as reading metadata cannot damage projects or cause unintended changes. Classified as Read with low severity.
From the tool's definition Tool name is 'get_metadata' and description states it 'Gets project metadata and XMP metadata for a project item' — the verb 'Gets' indicates pure data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_metadata, this is the rule to start with:
get_metadata is read-only, so it stays allowed. 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 get_metadata call is checked against it from then on.
Questions about get_metadata
Gets project metadata and XMP metadata for a project item. It is categorised as a Read tool in the Adobe Premiere Pro MCP Server, which means it retrieves data without modifying state.
get_metadata accepts 1 parameter: projectItemId. Required: 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 get_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.
get_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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