AI agents use create_sequence to create or update resources in Premiere Pro MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Premiere Pro MCP Server environment.
Creating a sequence in Premiere Pro is a write operation that adds a new, reversible object to the project. The action does not execute arbitrary code, delete data irreversibly, or move money. While sequences are foundational project elements, their creation is a standard, non-destructive edit operation that can be undone.
From the tool's definition Tool name 'create_sequence' and description 'Create a new sequence in Premiere Pro' indicate creation of a new reversible data structure within a project.
Documented attack patterns abuse exactly the kind of access create_sequence gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Premiere Pro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_sequence:
{
"version": "1",
"default": "deny",
"tools": {
"create_sequence": {
"limits": [
{
"counter": "create_sequence_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_sequence 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.
Free to start. No card required.
Create a new sequence in Premiere Pro. It is categorised as a Write tool in the Premiere Pro MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Premiere Pro MCP Server MCP server in PolicyLayer and add a rule for create_sequence: 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 Premiere Pro MCP Server. Nothing to install.
create_sequence 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 create_sequence 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 create_sequence. 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.
create_sequence is provided by the Premiere Pro MCP Server MCP server (jordanl61/premiere-pro-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Premiere Pro MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Premiere Pro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.