get_encoder_presets
Discovers readable user Adobe Media Encoder .epr presets from local AME preset folders. Factory preset enumeration is not claimed complete.
This record as markdown: /tools/adobe-premiere-pro-mcp/get-encoder-presets.md
What get_encoder_presets does on Adobe Premiere Pro
AI agents call get_encoder_presets 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 |
|---|---|---|---|
directories | array | — | Optional absolute directories to scan instead of the default user AME preset folders. Intended for tests and advanced setups. |
Parameters from the server's own tool schema.
Why get_encoder_presets is rated Low
This tool retrieves and lists preset configuration files from the local filesystem. It performs a passive discovery operation with no capability to modify, delete, or execute actions. The blast radius is minimal—an AI agent could only learn about available presets, not cause harm through their retrieval. This is a straightforward Read category tool.
From the tool's definition Tool description explicitly states it 'Discovers readable user Adobe Media Encoder .epr presets' - a query/retrieval operation that enumerates existing preset files without modifying or executing them.
Attacks that exploit this kind of access
The rule that runs get_encoder_presets 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_encoder_presets, this is the rule to start with:
get_encoder_presets 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_encoder_presets call is checked against it from then on.
Questions about get_encoder_presets
Discovers readable user Adobe Media Encoder .epr presets from local AME preset folders. Factory preset enumeration is not claimed complete. It is categorised as a Read tool in the Adobe Premiere Pro MCP Server, which means it retrieves data without modifying state.
get_encoder_presets accepts 1 parameter: directories. 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_encoder_presets: 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_encoder_presets 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_encoder_presets 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_encoder_presets. 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_encoder_presets 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