New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_camera_options

Set common camera options: zoom, depth of field, focus distance, aperture, blur level.

SERVERAe SOURCE@synthetic-ai/ae-mcp
Medium RISK CLASS
Category Write
Parameters 102 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/synthetic-ai-ae-mcp/set-camera-options.md

What set_camera_options does on Ae

AI agents use set_camera_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.

ParameterTypeRequiredDescription
save boolean Save after updating. Defaults to false.
zoom number
aperture number
compName string Yes Composition name.
blurLevel number
layerName string Yes Camera layer name.
timeoutMs number Process timeout in milliseconds. Defaults to 120000.
projectPath string Optional absolute path to an .aep file to open first.
depthOfField boolean
focusDistance number

Parameters from the server's own tool schema.

Why set_camera_options is rated Medium

An AI agent can call set_camera_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 (10 properties)

Questions about set_camera_options

What does the set_camera_options tool do? +

Set common camera options: zoom, depth of field, focus distance, aperture, blur level. 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.

What parameters does set_camera_options accept? +

set_camera_options accepts 10 parameters: save, zoom, aperture, compName, blurLevel, layerName, timeoutMs, projectPath, depthOfField, focusDistance. Required: compName, layerName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_camera_options? +

Register the Ae MCP server in PolicyLayer and add a rule for set_camera_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.

What risk level is set_camera_options? +

set_camera_options is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_camera_options? +

Yes. Add a rate_limit block to the set_camera_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.

How do I block set_camera_options completely? +

Set action: deny in the PolicyLayer policy for set_camera_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.

What MCP server provides set_camera_options? +

set_camera_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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ae's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.