anim_tree_create
Add an AnimationTree node under a parent (undoable) with a fresh tree_root graph. root_type "blend_tree" (AnimationNodeBlendTree) or "state_machine" (AnimationNodeStateMachine). Created inactive by default; set anim_player_path to the AnimationPlayer it should drive.
This record as markdown: /tools/breakpoint-mcp/anim-tree-create.md
What anim_tree_create does on Breakpoint
AI agents use anim_tree_create 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 | — | Node name (default "AnimationTree") |
active | boolean | — | Whether the tree processes immediately (default false) |
root_type | string | — | tree_root graph type (default blend_tree) |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
anim_player_path | string | — | NodePath to the AnimationPlayer this tree drives, relative to the AnimationTree node |
Parameters from the server's own tool schema.
Why anim_tree_create is rated Medium
This tool creates a new AnimationTree node, which is a modification to the scene/project structure. It is reversible (undoable), placing it in the Write category rather than Destructive. The severity is medium because inappropriate use could corrupt animation structures or create unexpected behaviors in the animation system, but the impact is confined to animation trees and can be undone.
From the tool's definition Tool description states 'Add an AnimationTree node under a parent (undoable)' and 'Created inactive by default; set anim_player_path to the AnimationPlayer it should drive.' The undoable qualifier and creation of a node confirms this is a Write operation that…
Attacks that exploit this kind of access
The rule that runs anim_tree_create 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_tree_create, this is the rule to start with:
anim_tree_create 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_tree_create call is checked against it from then on.
Questions about anim_tree_create
Add an AnimationTree node under a parent (undoable) with a fresh tree_root graph. root_type "blend_tree" (AnimationNodeBlendTree) or "state_machine" (AnimationNodeStateMachine). Created inactive by default; set anim_player_path to the AnimationPlayer it should drive. 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_tree_create accepts 5 parameters: name, active, root_type, parent_path, anim_player_path. Required: parent_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_tree_create: 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_tree_create 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_tree_create 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_tree_create. 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_tree_create 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