anim_delete
Delete an Animation from an AnimationPlayer's library (undoable). DESTRUCTIVE — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/anim-delete.md
What anim_delete does on Breakpoint
AI agents call anim_delete 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 |
|---|---|---|---|
name | string | Yes | Animation name |
confirm | boolean | — | Skip the confirmation prompt (auto-approve) |
library | string | — | Animation library name (default "") |
player_path | string | Yes | AnimationPlayer node path relative to the scene root |
Parameters from the server's own tool schema.
Why anim_delete is rated Critical
An AI agent that decides to call anim_delete doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Breakpoint is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs anim_delete 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_delete, this is the rule to start with:
anim_delete 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_delete call is checked against it from then on.
Questions about anim_delete
Delete an Animation from an AnimationPlayer's library (undoable). DESTRUCTIVE — gated by confirmation. 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_delete accepts 4 parameters: name, confirm, library, player_path. Required: name, 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_delete: 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_delete 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_delete 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_delete. 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_delete 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