setup_environment
Configure the WorldEnvironment for the 3D scene
This record as markdown: /tools/keeveeg-godot-mcp/setup-environment.md
What setup_environment does on Godot
AI agents use setup_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 | WorldEnvironment node path |
properties | object | Yes | Environment properties (background_mode, background_color, ambient_light_color, fog_enabled, glow_enabled, etc.) |
Parameters from the server's own tool schema.
Why setup_environment is rated Medium
This tool modifies (configures) the WorldEnvironment node in a Godot 3D scene, which is a reversible write operation. It does not execute arbitrary code, delete data, or perform financial transactions. The severity is medium because misconfiguration could affect scene rendering/behavior, but changes are reversible.
From the tool's definition Tool name 'setup_environment' combined with description 'Configure the WorldEnvironment for the 3D scene' indicates modification of scene configuration settings.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs setup_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 setup_environment, this is the rule to start with:
setup_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 setup_environment call is checked against it from then on.
Questions about setup_environment
Configure the WorldEnvironment for the 3D 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.
setup_environment accepts 2 parameters: path, properties. Required: path, properties. 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 setup_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.
setup_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 setup_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 setup_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.
setup_environment 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