AI agents use add_animation_track 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 |
|---|---|---|---|
interp | object | — | Interpolation method |
scene_path | string | Yes | Path to .tscn scene file |
track_path | string | Yes | Node property path to animate (e.g. ".:position", "Sprite2D:modulate") |
track_type | object | — | Track type |
animation_name | string | Yes | Name of the animation in AnimationPlayer |
Parameters from the server's own tool schema.
This tool creates or modifies animation tracks, which is a reversible change to project data. It does not execute arbitrary code, delete data irreversibly, or move money. Among the sibling tools (add_animation_library, add_audio_bus, add_autoload, etc.), all are Write operations that extend/configure Godot project structure.
From the tool's definition Tool name 'add_animation_track' and description 'Add track to animation' indicate creation/modification of animation data within Godot projects. This is a reversible write operation that creates new animation track resources.
Attacks that exploit this kind of access
Add track to animation. 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_animation_track accepts 5 parameters: interp, scene_path, track_path, track_type, animation_name. Required: scene_path, track_path, animation_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_animation_track: 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_animation_track 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_animation_track 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_animation_track. 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_animation_track is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
add_animation_track is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →