editor_get_project_setting
Read a project setting via editor API.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-get-project-setting.md
What editor_get_project_setting does on Godot
AI agents call editor_get_project_setting to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes |
Parameters from the server's own tool schema.
Why editor_get_project_setting is rated Low
This tool retrieves project settings through the Godot editor API with no side effects. It is a simple data query operation that does not modify, execute, or delete anything. The blast radius of misuse is minimal—an agent could only read configuration values that are already accessible within the project.
From the tool's definition Tool name contains 'get' and description explicitly states 'Read a project setting via editor API.' The action is to retrieve data without modification.
Attacks that exploit this kind of access
The rule that runs editor_get_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_get_project_setting, this is the rule to start with:
editor_get_project_setting is read-only, so it stays allowed. 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_get_project_setting call is checked against it from then on.
Questions about editor_get_project_setting
Read a project setting via editor API. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
editor_get_project_setting accepts 1 parameter: key. Required: key. 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_get_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_get_project_setting is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the editor_get_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_get_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_get_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