render_comp_range
Render a composition frame range with aerender.exe for quick automated verification.
This record as markdown: /tools/synthetic-ai-ae-mcp/render-comp-range.md
What render_comp_range does on Ae
AI agents use render_comp_range to create or update resources in Ae, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ae environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
reuse | boolean | — | Ask aerender to reuse the running AE instance. Defaults to false. |
verbose | string | — | Optional verbose flag, e.g. ERRORS or ERRORS_AND_PROGRESS. |
compName | string | Yes | Composition name to render. |
endFrame | number | — | Optional end frame. |
timeoutMs | number | — | Process timeout in milliseconds. Defaults to 1800000. |
outputPath | string | Yes | Absolute output path. |
startFrame | number | — | Optional start frame. |
projectPath | string | Yes | Absolute path to an .aep file. |
outputModule | string | — | Optional output module template name. |
frameIncrement | number | — | Optional frame increment. |
renderSettings | string | — | Optional render settings template name. |
Parameters from the server's own tool schema.
Why render_comp_range is rated Medium
An AI agent can call render_comp_range faster than any human can review: one bad instruction and it creates or modifies resources in Ae by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs render_comp_range safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_comp_range, this is the rule to start with:
render_comp_range stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every render_comp_range call is checked against it from then on.
Questions about render_comp_range
Render a composition frame range with aerender.exe for quick automated verification. It is categorised as a Write tool in the Ae MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
render_comp_range accepts 11 parameters: reuse, verbose, compName, endFrame, timeoutMs, outputPath, startFrame, projectPath, outputModule, frameIncrement, renderSettings. Required: compName, outputPath, projectPath. The full parameter table on this page comes from the server's own tool schema.
Register the Ae MCP server in PolicyLayer and add a rule for render_comp_range: 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.
render_comp_range is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the render_comp_range 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_comp_range. 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_comp_range 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.
This server
Across the catalogue