This record as markdown: /tools/yanhuifair-godot-mcp/create-scene.md
What create_scene does on Godot
AI agents use create_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 | Output path for new scene (relative to project root, e.g. "scenes/main.tscn") |
template | string | Yes | Root node type template |
root_name | object | — | Custom root node name (default: derived from template) |
Parameters from the server's own tool schema.
Why create_scene is rated Medium
This tool creates new scenes, which are reversible modifications to the project structure. Scenes can be deleted or replaced, so this is Write rather than Destructive. The severity is high because scene creation can impact project structure and load times, and an agent creating many scenes could degrade performance or cause confusion in project organization.
From the tool's definition Tool name 'create_scene' and description 'Create a new scene from template' indicate creation of new data structures within the Godot project.
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (template)
Attacks that exploit this kind of access
The rule that runs create_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 create_scene, this is the rule to start with:
create_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 create_scene call is checked against it from then on.
Questions about create_scene
Create a new scene from template. 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.
create_scene accepts 3 parameters: path, template, root_name. Required: path, template. 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 create_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.
create_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 create_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 create_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.
create_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