List the video transition matchNames installed in Premiere Pro
AI agents call list_available_transitions to retrieve information from Media-Editor-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of available video transitions in Premiere Pro. It returns information about installed transitions without side effects, data modification, or code execution. The blast radius of misuse is minimal—an agent could only discover what transitions exist, which is non-sensitive metadata about the editing environment.
From the tool's definition Tool name is 'list_available_transitions' and description states 'List the video transition matchNames installed in Premiere Pro' — it retrieves and queries installed transitions without modifying or executing any operations.
Attacks that exploit this kind of access
List the video transition matchNames installed in Premiere Pro. It is categorised as a Read tool in the Media-Editor-MCP MCP Server, which means it retrieves data without modifying state.
Register the Media-Editor- MCP server in PolicyLayer and add a rule for list_available_transitions: 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 Media-Editor-MCP. Nothing to install.
list_available_transitions 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 list_available_transitions 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 list_available_transitions. 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.
list_available_transitions is provided by the Media-Editor- MCP server (nguyenph88/media-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →