Get project bin structure and organization
AI agents call get_project_bins to retrieve information from Premiere Pro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata about how media is organized within Premiere Pro project bins. It performs no side effects, creates no data, executes no code, and modifies nothing. It is a straightforward information query operation with minimal security risk, even if misused by an agent.
From the tool's definition Tool name 'get_project_bins' and description 'Get project bin structure and organization' indicate a retrieval operation. The verb 'Get' and lack of any modification, deletion, or execution keywords confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access get_project_bins 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 get_project_bins:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_bins": {}
}
} get_project_bins is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get project bin structure and organization. It is categorised as a Read tool in the Premiere Pro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Premiere Pro MCP Server MCP server in PolicyLayer and add a rule for get_project_bins: 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.
get_project_bins 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_project_bins 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_project_bins. 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_project_bins 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.