List all sequences in the open Premiere project with their track counts and frame rates.
AI agents call list_sequences 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 operation that retrieves and displays information about video sequences. It queries project metadata (track counts, frame rates) but does not create, modify, delete, or execute any changes to the project. The action is purely informational with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'list_sequences' and description 'List all sequences in the open Premiere project with their track counts and frame rates' indicate a query operation that retrieves metadata about existing project structures without modifying or executing any…
Attacks that exploit this kind of access
List all sequences in the open Premiere project with their track counts and frame rates. 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_sequences: 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_sequences 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_sequences 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_sequences. 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_sequences 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 →