anim_remove_key
Remove a keyframe by index from a track (undoable).
This record as markdown: /tools/breakpoint-mcp/anim-remove-key.md
What anim_remove_key does on Breakpoint
AI agents call anim_remove_key to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | integer | Yes | Key index within the track |
name | string | Yes | Animation name |
track | integer | Yes | Track index |
confirm | boolean | — | Skip the confirmation prompt (auto-approve) |
library | string | — | Animation library name (default "") |
player_path | string | Yes | AnimationPlayer node path |
Parameters from the server's own tool schema.
Why anim_remove_key is rated Critical
The tool removes a keyframe from an animation track. Although the description says 'undoable', the primary action is deletion/removal of data. 'Undoable' reduces severity slightly but the operation is still destructive in nature — it deletes a keyframe. Severity is medium since it affects animation data within a game project, not system-level or financial data.
From the tool's definition 'Remove a keyframe by index from a track' — removes data from an animation track
Attacks that exploit this kind of access
The rule that runs anim_remove_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_remove_key, this is the rule to start with:
anim_remove_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every anim_remove_key call is checked against it from then on.
Questions about anim_remove_key
Remove a keyframe by index from a track (undoable). It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
anim_remove_key accepts 6 parameters: key, name, track, confirm, library, player_path. Required: key, name, 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_remove_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_remove_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the anim_remove_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_remove_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_remove_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.
Across the catalogue