batch_keyframe_offset
Shift all keyframes on specified layers (or all layers) by a time offset in seconds.
This record as markdown: /tools/synthetic-ai-ae-mcp/batch-keyframe-offset.md
What batch_keyframe_offset does on Ae
AI agents use batch_keyframe_offset 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 | — | |
layerNames | array | — | Layer names to affect (empty = all layers) |
projectPath | string | — | |
offsetSeconds | number | Yes | Time to shift keyframes by (positive = later, negative = earlier) |
propertyFilter | string | — | Optional property match name filter (e.g. 'ADBE Position') |
Parameters from the server's own tool schema.
Why batch_keyframe_offset is rated Medium
An AI agent can call batch_keyframe_offset 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs batch_keyframe_offset 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 batch_keyframe_offset, this is the rule to start with:
batch_keyframe_offset 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 batch_keyframe_offset call is checked against it from then on.
Questions about batch_keyframe_offset
Shift all keyframes on specified layers (or all layers) by a time offset in seconds. 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.
batch_keyframe_offset accepts 7 parameters: save, compName, timeoutMs, layerNames, projectPath, offsetSeconds, propertyFilter. Required: compName, offsetSeconds. 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 batch_keyframe_offset: 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.
batch_keyframe_offset 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 batch_keyframe_offset 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 batch_keyframe_offset. 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.
batch_keyframe_offset 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