manage_proxies
Checks proxy status, attaches a proxy file, or gets the proxy path for a project item.
This record as markdown: /tools/adobe-premiere-pro-mcp/manage-proxies.md
What manage_proxies does on Adobe Premiere Pro
AI agents use manage_proxies 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 |
|---|---|---|---|
action | string | Yes | The proxy action: check status, attach a proxy, or get proxy path |
proxyPath | string | — | The absolute path to the proxy file (required for attach action) |
projectItemId | string | Yes | The ID of the project item |
Parameters from the server's own tool schema.
Why manage_proxies is rated Medium
Proxy attachment modifies project metadata and asset associations reversibly—files are not deleted and changes can be undone through the undo system in Premiere Pro. This is characteristic of Write operations (creates or modifies data reversibly).
From the tool's definition Tool performs actions on project items: 'attaches a proxy file' indicates modification of media asset configuration.
Attacks that exploit this kind of access
The rule that runs manage_proxies 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 manage_proxies, this is the rule to start with:
manage_proxies 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 manage_proxies call is checked against it from then on.
Questions about manage_proxies
Checks proxy status, attaches a proxy file, or gets the proxy path for 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.
manage_proxies accepts 3 parameters: action, proxyPath, projectItemId. Required: action, 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 manage_proxies: 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.
manage_proxies 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 manage_proxies 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 manage_proxies. 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.
manage_proxies 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