render_sequence
Queue a Movie Render Queue job for a sequence.
This record as markdown: /tools/jjpxdev-unreal-mcp/render-sequence.md
What render_sequence does on Unreal
AI agents invoke render_sequence to trigger actions in Unreal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
sequence_path | string | Yes | LevelSequence asset path |
output_directory | string | — | Output directory for rendered frames |
Parameters from the server's own tool schema.
Why render_sequence is rated High
This tool triggers an external rendering operation in Unreal Engine's Movie Render Queue, which executes a potentially long-running compute job. It's not simply reading or writing data, but actively initiating a pipeline execution. Misuse could consume significant CPU/GPU resources or produce unintended output files, warranting a high severity rating.
From the tool's definition Queue a Movie Render Queue job for a sequence
Attacks that exploit this kind of access
The rule that runs render_sequence safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_sequence, this is the rule to start with:
render_sequence stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unreal, apply this rule, and every render_sequence call is checked against it from then on.
Questions about render_sequence
Queue a Movie Render Queue job for a sequence. It is categorised as a Execute tool in the Unreal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
render_sequence accepts 2 parameters: sequence_path, output_directory. Required: sequence_path. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for render_sequence: 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 Unreal. Nothing to install.
render_sequence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the render_sequence 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 render_sequence. 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.
render_sequence is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
Across the catalogue