Low Risk

get_render_queue

Get current render queue status and items

How to control get_render_queue ↓

What get_render_queue does on Premiere Pro MCP Server

AI agents call get_render_queue 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.

Low Risk

Why get_render_queue needs a policy

This tool retrieves information about the current state of the render queue in Adobe Premiere Pro. It performs a read-only operation that queries existing data without creating, modifying, executing, or deleting any resources. The 'get' prefix and passive voice ('Get...status and items') confirm it is purely informational with no side effects.

From the tool's definition Tool name 'get_render_queue' and description 'Get current render queue status and items' indicate a query/retrieval operation with no modification or execution capability.

Documented attack patterns abuse exactly the kind of access get_render_queue gives an agent:

How to control get_render_queue

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_render_queue:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_render_queue": {}
  }
}

get_render_queue is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Premiere Pro MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_render_queue

What does the get_render_queue tool do? +

Get current render queue status and items. It is categorised as a Read tool in the Premiere Pro MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_render_queue? +

Register the Premiere Pro MCP Server MCP server in PolicyLayer and add a rule for get_render_queue: 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.

What risk level is get_render_queue? +

get_render_queue is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_render_queue? +

Yes. Add a rate_limit block to the get_render_queue 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.

How do I block get_render_queue completely? +

Set action: deny in the PolicyLayer policy for get_render_queue. 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.

What MCP server provides get_render_queue? +

get_render_queue 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.

Enforce policy on every Premiere Pro MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.