set_light_options
Set common light options: intensity, color, cone angle/feather, shadow darkness/diffusion.
This record as markdown: /tools/synthetic-ai-ae-mcp/set-light-options.md
What set_light_options does on Ae
AI agents use set_light_options 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 |
|---|---|---|---|
save | boolean | — | Save after updating. Defaults to false. |
color | array | — | RGB array. |
compName | string | Yes | Composition name. |
coneAngle | number | — | |
intensity | number | — | |
layerName | string | Yes | Light layer name. |
timeoutMs | number | — | Process timeout in milliseconds. Defaults to 120000. |
coneFeather | number | — | |
projectPath | string | — | Optional absolute path to an .aep file to open first. |
castsShadows | boolean | — | |
shadowDarkness | number | — | |
shadowDiffusion | number | — |
Parameters from the server's own tool schema.
Why set_light_options is rated Medium
An AI agent can call set_light_options 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 (12 properties)
Attacks that exploit this kind of access
The rule that runs set_light_options 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 set_light_options, this is the rule to start with:
set_light_options 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 set_light_options call is checked against it from then on.
Questions about set_light_options
Set common light options: intensity, color, cone angle/feather, shadow darkness/diffusion. 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.
set_light_options accepts 12 parameters: save, color, compName, coneAngle, intensity, layerName, timeoutMs, coneFeather, projectPath, castsShadows, shadowDarkness, shadowDiffusion. Required: compName, layerName. 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 set_light_options: 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.
set_light_options 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 set_light_options 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 set_light_options. 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.
set_light_options 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