get_clip_at_position
Gets the clip at a specific time position on a track.
This record as markdown: /tools/adobe-premiere-pro-mcp/get-clip-at-position.md
What get_clip_at_position does on Adobe Premiere Pro
AI agents call get_clip_at_position 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 |
|---|---|---|---|
time | number | Yes | The time position in seconds |
trackType | string | Yes | The type of track |
sequenceId | string | Yes | The ID of the sequence |
trackIndex | number | Yes | The track index (0-based) |
Parameters from the server's own tool schema.
Why get_clip_at_position is rated Low
This tool queries or retrieves information about a clip at a given timeline position in Adobe Premiere Pro. It has no side effects—it does not create, modify, delete, or execute any operations. It is purely informational, consistent with the Read category for tools that retrieve or query data without side effects.
From the tool's definition Tool name and description indicate retrieval: 'Gets the clip at a specific time position on a track.' No modifications, deletions, or external operations are performed.
Attacks that exploit this kind of access
The rule that runs get_clip_at_position 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_clip_at_position, this is the rule to start with:
get_clip_at_position 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_clip_at_position call is checked against it from then on.
Questions about get_clip_at_position
Gets the clip at a specific time position on a track. It is categorised as a Read tool in the Adobe Premiere Pro MCP Server, which means it retrieves data without modifying state.
get_clip_at_position accepts 4 parameters: time, trackType, sequenceId, trackIndex. Required: time, trackType, sequenceId, trackIndex. 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_clip_at_position: 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_clip_at_position 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_clip_at_position 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_clip_at_position. 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_clip_at_position 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