set_keyframes
Set multiple keyframes on a named layer property using an After Effects property path.
This record as markdown: /tools/synthetic-ai-ae-mcp/set-keyframes.md
What set_keyframes does on Ae
AI agents use set_keyframes 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 the project after updating. Defaults to false. |
compName | string | Yes | Composition name. |
keyframes | array | Yes | Array of { time, value } keyframes. |
layerName | string | Yes | Layer name. |
timeoutMs | number | — | Process timeout in milliseconds. Defaults to 120000. |
projectPath | string | — | Optional absolute path to an .aep file to open first. |
propertyPath | array | Yes | Property path, preferably match names, e.g. ["ADBE Transform Group", "ADBE Position"]. |
Parameters from the server's own tool schema.
Why set_keyframes is rated Medium
An AI agent can call set_keyframes 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.
Attacks that exploit this kind of access
The rule that runs set_keyframes 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_keyframes, this is the rule to start with:
set_keyframes 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_keyframes call is checked against it from then on.
Questions about set_keyframes
Set multiple keyframes on a named layer property using an After Effects property path. 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_keyframes accepts 7 parameters: save, compName, keyframes, layerName, timeoutMs, projectPath, propertyPath. Required: compName, keyframes, layerName, propertyPath. 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_keyframes: 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_keyframes 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_keyframes 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_keyframes. 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_keyframes 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