get_project_setting
Get a single project setting value by key (e.g. 'display/window/size/viewport_width')
This record as markdown: /tools/keeveeg-godot-mcp/get-project-setting.md
What get_project_setting does on Godot
AI agents call 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 | Project setting key path |
Parameters from the server's own tool schema.
Why get_project_setting is rated Low
This tool retrieves project settings without altering state, creating, deleting, or executing operations. It is a straightforward read operation on Godot project configuration. The sibling tools on this server (add_*) suggest this is part of a Godot editor integration, where querying settings poses minimal risk.
From the tool's definition Tool name 'get_project_setting' and description 'Get a single project setting value by key' indicates retrieval of configuration data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs 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 get_project_setting, this is the rule to start with:
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 get_project_setting call is checked against it from then on.
Questions about get_project_setting
Get a single project setting value by key (e.g. 'display/window/size/viewport_width'). It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
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 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.
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 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 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.
get_project_setting 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