anim_insert_key
Insert a keyframe on a track at a given time (undoable). A key already at that exact time is overwritten.
This record as markdown: /tools/breakpoint-mcp/anim-insert-key.md
What anim_insert_key does on Breakpoint
AI agents use anim_insert_key to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Animation name |
time | number | Yes | Key time in seconds |
track | integer | Yes | Track index |
value | object | — | Key value (JSON scalar, array, object, or a __type__-tagged Variant matching the track type) |
library | string | — | Animation library name (default "") |
transition | number | — | Transition curve exponent (default 1.0) |
player_path | string | Yes | AnimationPlayer node path |
Parameters from the server's own tool schema.
Why anim_insert_key is rated Medium
The tool creates or modifies animation track data (keyframes) in a reversible manner. The parenthetical '(undoable)' and context of animation editing confirm this is a Write operation rather than Destructive—changes can be undone. Severity is medium because misuse could corrupt animation sequences, but the impact is limited to animation data within the application and is recoverable via undo.
From the tool's definition Tool description states it 'Insert a keyframe on a track at a given time (undoable)' and explicitly notes that 'A key already at that exact time is overwritten.' This describes creation and modification of animation keyframe data.
Attacks that exploit this kind of access
The rule that runs anim_insert_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For anim_insert_key, this is the rule to start with:
anim_insert_key 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 Breakpoint, apply this rule, and every anim_insert_key call is checked against it from then on.
Questions about anim_insert_key
Insert a keyframe on a track at a given time (undoable). A key already at that exact time is overwritten. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
anim_insert_key accepts 7 parameters: name, time, track, value, library, transition, player_path. Required: name, time, track, player_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for anim_insert_key: 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 Breakpoint. Nothing to install.
anim_insert_key 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 anim_insert_key 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 anim_insert_key. 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.
anim_insert_key is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue