This record as markdown: /tools/chanceflow-godot-mcp/animation-create.md
What animation_create does on Godot
AI agents use animation_create 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.
Why animation_create is rated Medium
Creating animations modifies project state reversibly—new animations can be deleted or replaced. This is a Write operation rather than Read (no query), Execute (no arbitrary code or external command), or Destructive (reversible). Severity is medium because unintended animation creation could corrupt project workflows, but the blast radius is limited to animation assets and reversible.
From the tool's definition Tool name 'animation_create' indicates creation of new animation data within Godot. Sibling tools like 'animation_add_track', 'animation_set_keyframe', and 'animation_list' confirm this is part of the animation management subsystem.
Attacks that exploit this kind of access
The rule that runs animation_create 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 animation_create, this is the rule to start with:
animation_create 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 animation_create call is checked against it from then on.
Questions about animation_create
animation_create is a write tool on the Godot MCP server. 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.
Register the Godot MCP server in PolicyLayer and add a rule for animation_create: 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.
animation_create 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_create 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_create. 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_create is provided by the Godot MCP server (chanceflow/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