This record as markdown: /tools/keeveeg-godot-mcp/add-animation-track.md
What add_animation_track does on Godot
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 |
|---|---|---|---|
library | string | — | Animation library name (empty for default) |
property | string | — | Property path for value/bezier tracks (e.g. 'position:x') |
animation | string | Yes | Animation name |
track_type | string | Yes | Type of track to add |
player_path | string | Yes | AnimationPlayer node path |
Parameters from the server's own tool schema.
Why add_animation_track is rated Medium
This tool creates or modifies animation data by adding a track, which is a reversible operation. It falls under Write category as it creates new animation content. Severity is medium because misuse could corrupt game animations or create unintended animation behavior, but the effects are reversible and limited to animation assets rather than core game logic or data deletion.
From the tool's definition Tool name is 'add_animation_track' with description 'Add a track to an animation'. The verb 'add' indicates creation/modification of data within an animation resource.
Attacks that exploit this kind of access
The rule that runs add_animation_track 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_animation_track, this is the rule to start with:
add_animation_track 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_animation_track call is checked against it from then on.
Questions about add_animation_track
Add a track to an 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: library, property, animation, track_type, player_path. Required: animation, track_type, player_path. 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 (@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