This record as markdown: /tools/yanhuifair-godot-mcp/create-environment.md
What create_environment does on Godot
AI agents use create_environment 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 Environment .tres (e.g. "environments/default.tres") |
preset | object | — | Preset: default, stylized, dark, or bright |
Parameters from the server's own tool schema.
Why create_environment is rated Medium
This tool creates (writes) a new environment configuration from a preset, which is a reversible operation. It does not execute arbitrary code, delete data, or move financial assets. The severity is medium because an AI agent could create unwanted environment configurations that affect rendering, audio, or physics settings in the game project, requiring manual cleanup but no permanent damage.
From the tool's definition Tool name 'create_environment' and description 'Create Environment from preset' indicate creation of a new environment resource in Godot.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_environment 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_environment, this is the rule to start with:
create_environment 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_environment call is checked against it from then on.
Questions about create_environment
Create Environment from preset. 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_environment accepts 2 parameters: path, preset. 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_environment: 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_environment 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_environment 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_environment. 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_environment 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