add_state_machine_state
Add a state to an AnimationNodeStateMachine
This record as markdown: /tools/keeveeg-godot-mcp/add-state-machine-state.md
What add_state_machine_state does on Godot
AI agents use add_state_machine_state to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | AnimationTree node path |
animation | string | — | Animation name to assign to this state |
state_name | string | Yes | Name for the new state |
Parameters from the server's own tool schema.
Why add_state_machine_state is rated Medium
This tool creates or modifies animation state machine configuration in a Godot project, which is a reversible write operation. It doesn't execute arbitrary code, delete data, or move money. The severity is medium because misuse could corrupt animation logic and require manual repair, but the effect is confined to animation state management rather than core project integrity.
From the tool's definition Tool name 'add_state_machine_state' and description 'Add a state to an AnimationNodeStateMachine' indicate creation of a new state object within a game engine animation system.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs add_state_machine_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_state_machine_state, this is the rule to start with:
add_state_machine_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 Godot, apply this rule, and every add_state_machine_state call is checked against it from then on.
Questions about add_state_machine_state
Add a state to an AnimationNodeStateMachine. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_state_machine_state accepts 3 parameters: path, animation, state_name. Required: path, state_name. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for add_state_machine_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 Godot. Nothing to install.
add_state_machine_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 add_state_machine_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 add_state_machine_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.
add_state_machine_state is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue