rhino_render_queue_cancel
Cancel a running or queued render job.
This record as markdown: /tools/easehee-rhino-mcp/rhino-render-queue-cancel.md
What rhino_render_queue_cancel does on Rhino
AI agents call rhino_render_queue_cancel to permanently remove resources in Rhino, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why rhino_render_queue_cancel is rated Critical
Cancelling a render job is irreversible in the sense that the in-progress computation and any partial results are lost and cannot be recovered. This is a destructive action that terminates an ongoing process permanently, though its blast radius is limited to the render job itself rather than persistent data.
From the tool's definition Cancel a running or queued render job
Attacks that exploit this kind of access
The rule that runs rhino_render_queue_cancel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rhino, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rhino_render_queue_cancel, this is the rule to start with:
rhino_render_queue_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every rhino_render_queue_cancel call is checked against it from then on.
Questions about rhino_render_queue_cancel
Cancel a running or queued render job. It is categorised as a Destructive tool in the Rhino MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_render_queue_cancel: 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 Rhino. Nothing to install.
rhino_render_queue_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rhino_render_queue_cancel 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 rhino_render_queue_cancel. 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.
rhino_render_queue_cancel is provided by the Rhino MCP server (easehee/rhino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rhino, and thousands of servers like it.
Across the catalogue