create_scene
Create a new empty scene with a specified root node type
This record as markdown: /tools/keeveeg-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 | Path to save the scene (e.g. 'res://scenes/new.tscn') |
root_node_type | string | — | Root node type (e.g. 'Node2D', 'Control') |
Parameters from the server's own tool schema.
Why create_scene is rated Medium
This tool creates new scenes, which modifies the Godot project state reversibly. Scenes can be deleted or overwritten, making this a Write operation rather than Destructive. The medium severity reflects that while scene creation is reversible, misuse could clutter or corrupt a project structure.
From the tool's definition Tool name 'create_scene' and description 'Create a new empty scene with a specified root node type' indicate creation of new game objects/scenes in Godot engine.
Risk signalsAccepts file system path (path) · Admin/system-level operation
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 empty scene with a specified root node type. 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 2 parameters: path, root_node_type. Required: 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 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 (@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