find_project_item_by_name
Searches for project items by name. Useful for finding media files, sequences, or bins.
This record as markdown: /tools/adobe-premiere-pro-mcp/find-project-item-by-name.md
What find_project_item_by_name does on Adobe Premiere Pro
AI agents call find_project_item_by_name 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 |
|---|---|---|---|
name | string | Yes | The name to search for (case-insensitive partial match) |
type | string | — | Filter by item type |
Parameters from the server's own tool schema.
Why find_project_item_by_name is rated Low
This tool retrieves or queries project items based on name matching. It has no side effects—it does not create, modify, delete, execute code, or move data. It is purely a search/lookup operation, which is the definition of the Read category.
From the tool's definition Tool name 'find_project_item_by_name' and description 'Searches for project items by name. Useful for finding media files, sequences, or bins.' indicate a search/query operation with no data modification or execution.
Attacks that exploit this kind of access
The rule that runs find_project_item_by_name 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 find_project_item_by_name, this is the rule to start with:
find_project_item_by_name 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 find_project_item_by_name call is checked against it from then on.
Questions about find_project_item_by_name
Searches for project items by name. Useful for finding media files, sequences, or bins. It is categorised as a Read tool in the Adobe Premiere Pro MCP Server, which means it retrieves data without modifying state.
find_project_item_by_name accepts 2 parameters: name, type. Required: name. 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 find_project_item_by_name: 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.
find_project_item_by_name 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 find_project_item_by_name 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 find_project_item_by_name. 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.
find_project_item_by_name 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