editor_set_project_setting
Set a project setting via editor API (auto-saves).
This record as markdown: /tools/yanhuifair-godot-mcp/editor-set-project-setting.md
What editor_set_project_setting does on Godot
AI agents use editor_set_project_setting 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 |
|---|---|---|---|
key | string | Yes | |
value | string | Yes |
Parameters from the server's own tool schema.
Why editor_set_project_setting is rated Medium
This tool creates or modifies project settings data reversibly through the editor API. While it auto-saves, the changes are not destructive (settings can be reverted/reconfigured), and it does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states 'Set a project setting via editor API (auto-saves)' — this modifies project configuration which is persisted automatically.
Attacks that exploit this kind of access
The rule that runs editor_set_project_setting 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 editor_set_project_setting, this is the rule to start with:
editor_set_project_setting 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 editor_set_project_setting call is checked against it from then on.
Questions about editor_set_project_setting
Set a project setting via editor API (auto-saves). 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.
editor_set_project_setting accepts 2 parameters: key, value. Required: key, value. 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 editor_set_project_setting: 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.
editor_set_project_setting 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 editor_set_project_setting 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 editor_set_project_setting. 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.
editor_set_project_setting 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