Create, inspect, and configure AnimationTree state machines
AI agents use animation_state_machine to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool can create and configure animation state machines, which are reversible modifications to Godot project assets. It does not execute arbitrary code, delete assets, or move money. Severity is medium because misconfiguration of animation state machines could cause runtime issues or require rework, but the changes are reversible and localized to animation logic.
From the tool's definition Tool description states 'Create, inspect, and configure AnimationTree state machines' — the verbs 'create' and 'configure' indicate the tool can modify project assets (animation state machines) reversibly.
Documented attack patterns abuse exactly the kind of access animation_state_machine gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for animation_state_machine:
{
"version": "1",
"default": "deny",
"tools": {
"animation_state_machine": {
"limits": [
{
"counter": "animation_state_machine_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}animation_state_machine 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.
Free to start. No card required.
Create, inspect, and configure AnimationTree state machines. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for animation_state_machine: 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 Devtool. Nothing to install.
animation_state_machine 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 animation_state_machine 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 animation_state_machine. 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.
animation_state_machine is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.