New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_render_queue_item

Remove a render queue item by 1-based index.

SERVERAe SOURCE@synthetic-ai/ae-mcp
Critical RISK CLASS
Category Destructive
Parameters 41 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/remove-render-queue-item.md

What remove_render_queue_item does on Ae

AI agents call remove_render_queue_item to permanently remove resources in Ae, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
save boolean
timeoutMs number
queueIndex number Yes 1-based render queue item index.
projectPath string

Parameters from the server's own tool schema.

Why remove_render_queue_item is rated Critical

An AI agent that decides to call remove_render_queue_item doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ae is gone. There is no undo for destructive operations.

Questions about remove_render_queue_item

What does the remove_render_queue_item tool do? +

Remove a render queue item by 1-based index. It is categorised as a Destructive tool in the Ae MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does remove_render_queue_item accept? +

remove_render_queue_item accepts 4 parameters: save, timeoutMs, queueIndex, projectPath. Required: queueIndex. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remove_render_queue_item? +

Register the Ae MCP server in PolicyLayer and add a rule for remove_render_queue_item: 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 Ae. Nothing to install.

What risk level is remove_render_queue_item? +

remove_render_queue_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_render_queue_item? +

Yes. Add a rate_limit block to the remove_render_queue_item 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 remove_render_queue_item completely? +

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

remove_render_queue_item is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ae, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ae's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.