This record as markdown: /tools/yanhuifair-godot-mcp/edit-scene.md
What edit_scene does on Godot
AI agents use edit_scene 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 |
|---|---|---|---|
path | string | Yes | Path to .tscn file to edit (relative to project root) |
operations | array | Yes | List of scene operations to apply |
Parameters from the server's own tool schema.
Why edit_scene is rated Medium
This tool creates or modifies scene data reversibly. It does not delete (Destructive), execute arbitrary code (Execute), or move money (Financial). However, batch edits to a scene can have broad impact on game structure and behavior, justifying 'high' severity—a misused batch operation could corrupt or significantly alter game scenes.
From the tool's definition Tool description states 'Apply batch operations to a scene' — directly modifies scene state in Godot. The name 'edit_scene' and context of sibling tools (add_animation_library, add_node, add_script_export, etc.) confirm this performs write operations on game…
Risk signalsAccepts file system path (path) · High parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs edit_scene 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 edit_scene, this is the rule to start with:
edit_scene 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 edit_scene call is checked against it from then on.
Questions about edit_scene
Apply batch operations to a scene. 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.
edit_scene accepts 2 parameters: path, operations. Required: path, operations. 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 edit_scene: 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.
edit_scene 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 edit_scene 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 edit_scene. 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.
edit_scene 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