This record as markdown: /tools/yanhuifair-godot-mcp/set-keyframe.md
What set_keyframe does on Godot
AI agents use set_keyframe 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 |
|---|---|---|---|
time | number | Yes | Time in seconds |
value | string | Yes | Value at keyframe (e.g. "Vector2(100, 0)", "1.5") |
easing | object | — | Easing weight (0=custom, 1=auto, >1=ease in, <-1=ease out) |
scene_path | string | Yes | Path to .tscn scene file |
track_index | number | Yes | Track index (0-based) |
animation_name | string | Yes | Animation name |
Parameters from the server's own tool schema.
Why set_keyframe is rated Medium
This tool modifies animation keyframe data within a Godot project. While reversible (keyframes can be removed or adjusted), it constitutes a write operation that alters project state. Severity is medium because unintended keyframe modifications could corrupt animations but are not destructive (the original can be recovered) and don't execute arbitrary code or affect system resources beyond the Godot project scope.
From the tool's definition set_keyframe sets a keyframe on an animation track, which modifies animation data in a reversible manner. This is a data modification operation that can be undone through standard animation editing workflows.
Attacks that exploit this kind of access
The rule that runs set_keyframe 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 set_keyframe, this is the rule to start with:
set_keyframe 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 set_keyframe call is checked against it from then on.
Questions about set_keyframe
Set keyframe on track. 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.
set_keyframe accepts 6 parameters: time, value, easing, scene_path, track_index, animation_name. Required: time, value, scene_path, track_index, 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 set_keyframe: 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.
set_keyframe 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 set_keyframe 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 set_keyframe. 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.
set_keyframe 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue