copy_keyframes
Copy keyframes from one property to another (same or different layer), with optional time offset.
This record as markdown: /tools/synthetic-ai-ae-mcp/copy-keyframes.md
What copy_keyframes does on Ae
AI agents use copy_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 | — | |
compName | string | Yes | |
timeoutMs | number | — | |
sourcePath | array | Yes | Source property path. |
targetPath | array | — | Target property path. Defaults to sourcePath. |
timeOffset | number | — | Time offset in seconds to apply to copied keyframes. Defaults to 0. |
projectPath | string | — | |
sourceLayer | string | Yes | |
targetLayer | string | — | Defaults to sourceLayer. |
Parameters from the server's own tool schema.
Why copy_keyframes is rated Medium
An AI agent can call copy_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 copy_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 copy_keyframes, this is the rule to start with:
copy_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 copy_keyframes call is checked against it from then on.
Questions about copy_keyframes
Copy keyframes from one property to another (same or different layer), with optional time offset. 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.
copy_keyframes accepts 9 parameters: save, compName, timeoutMs, sourcePath, targetPath, timeOffset, projectPath, sourceLayer, targetLayer. Required: compName, sourcePath, sourceLayer. 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 copy_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.
copy_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 copy_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 copy_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.
copy_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