Reports whether render queue monitoring is available. This currently returns guidance for Adobe Media Encoder rather than live queue telemetry.
AI agents call get_render_queue_status to retrieve information from Premiere MCP 剪辑助手 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_render_queue_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Reports whether render queue monitoring is available. This currently returns guidance for Adobe Media Encoder rather than live queue telemetry. It is categorised as a Read tool in the Premiere MCP 剪辑助手 MCP Server, which means it retrieves data without modifying state.
Register the Premiere MCP 剪辑助手 MCP server in PolicyLayer and add a rule for get_render_queue_status: 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 MCP 剪辑助手. Nothing to install.
get_render_queue_status 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_render_queue_status 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_render_queue_status. 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_render_queue_status is provided by the Premiere MCP 剪辑助手 MCP server (sylphiette269/premiere-mcp-editor-cn). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.