move_item_to_bin
Moves a project item into a different bin (folder).
This record as markdown: /tools/adobe-premiere-pro-mcp/move-item-to-bin.md
What move_item_to_bin does on Adobe Premiere Pro
AI agents use move_item_to_bin to create or update resources in Adobe Premiere Pro, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adobe Premiere Pro environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
targetBinId | string | Yes | The ID of the destination bin |
projectItemId | string | Yes | The ID of the project item to move |
Parameters from the server's own tool schema.
Why move_item_to_bin is rated Medium
The tool modifies project metadata/organization by moving items between bins, which is a Write operation (reversible change to data structure). It does not delete, execute code, or access external systems. Severity is medium because incorrect moves could disorganize a complex project and create confusion, but the operation is easily undoable and does not destroy content or execute arbitrary commands.
From the tool's definition Tool description states 'Moves a project item into a different bin (folder)' — this modifies the organizational structure of project data within Adobe Premiere Pro by relocating items between containers.
Attacks that exploit this kind of access
The rule that runs move_item_to_bin 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 move_item_to_bin, this is the rule to start with:
move_item_to_bin 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Premiere Pro, apply this rule, and every move_item_to_bin call is checked against it from then on.
Questions about move_item_to_bin
Moves a project item into a different bin (folder). It is categorised as a Write tool in the Adobe Premiere Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
move_item_to_bin accepts 2 parameters: targetBinId, projectItemId. Required: targetBinId, projectItemId. 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 move_item_to_bin: 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.
move_item_to_bin 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 move_item_to_bin 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 move_item_to_bin. 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.
move_item_to_bin 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