anim_statemachine_add_state
Add a state to an AnimationNodeStateMachine (undoable). Targets the AnimationTree's tree_root when it is a state machine, or a nested state-machine node via state_machine. Defaults the state to an AnimationNodeAnimation; pass animation to bind a clip.
This record as markdown: /tools/breakpoint-mcp/anim-statemachine-add-state.md
What anim_statemachine_add_state does on Breakpoint
AI agents use anim_statemachine_add_state 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 |
|---|---|---|---|
position | array | — | Graph editor position [x, y] (default [0, 0]) |
animation | string | — | For an AnimationNodeAnimation state: the animation name to play |
node_type | string | — | AnimationNode subclass for the state (default AnimationNodeAnimation) |
tree_path | string | Yes | AnimationTree node path relative to the scene root |
state_name | string | Yes | Unique state name within the state machine |
state_machine | string | — | Name of a nested AnimationNodeStateMachine node within tree_root; omit to target tree_root itself |
Parameters from the server's own tool schema.
Why anim_statemachine_add_state is rated Medium
This tool creates a new state within an animation state machine, which modifies the animation tree structure. The operation is explicitly marked as undoable, confirming it is reversible (Write category). The severity is medium because misuse could corrupt animation logic or create unexpected animation behaviors, but the damage is contained to animation state configuration and is reversible.
From the tool's definition Tool description states "Add a state to an AnimationNodeStateMachine (undoable)" - the verb "Add" and explicit mention of "undoable" indicate reversible data modification.
Attacks that exploit this kind of access
The rule that runs anim_statemachine_add_state 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_statemachine_add_state, this is the rule to start with:
anim_statemachine_add_state 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_statemachine_add_state call is checked against it from then on.
Questions about anim_statemachine_add_state
Add a state to an AnimationNodeStateMachine (undoable). Targets the AnimationTree's tree_root when it is a state machine, or a nested state-machine node via state_machine. Defaults the state to an AnimationNodeAnimation; pass animation to bind a clip. 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_statemachine_add_state accepts 6 parameters: position, animation, node_type, tree_path, state_name, state_machine. Required: tree_path, state_name. 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_statemachine_add_state: 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_statemachine_add_state 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_statemachine_add_state 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_statemachine_add_state. 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_statemachine_add_state 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