rhino_render_queue_status
Inspect a queued render job's status, progress, and completed frames.
This record as markdown: /tools/easehee-rhino-mcp/rhino-render-queue-status.md
What rhino_render_queue_status does on Rhino
AI agents call rhino_render_queue_status to retrieve information from Rhino without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why rhino_render_queue_status is rated Low
This tool only retrieves and queries the state of an existing render job. It has no side effects, does not modify any data, does not execute rendering operations, and does not delete or overwrite anything. The verb 'inspect' confirms read-only intent. Misuse by an AI agent would be minimal—at worst, it could spam status checks, which is a low blast radius.
From the tool's definition Tool name contains 'status' and description states 'Inspect a queued render job's status, progress, and completed frames' — purely informational retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs rhino_render_queue_status 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_status, this is the rule to start with:
rhino_render_queue_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every rhino_render_queue_status call is checked against it from then on.
Questions about rhino_render_queue_status
Inspect a queued render job's status, progress, and completed frames. It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_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 Rhino. Nothing to install.
rhino_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 rhino_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 rhino_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.
rhino_render_queue_status 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.
This server
Across the catalogue