This record as markdown: /tools/chanceflow-godot-mcp/project-setting-set.md
What project_setting_set does on Godot
AI agents use project_setting_set 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.
Why project_setting_set is rated Medium
This tool creates or modifies project settings in the project.godot configuration file. While changes are theoretically reversible (settings can be changed back), misuse could disable critical features, break project functionality, or introduce security vulnerabilities.
From the tool's definition Tool name 'project_setting_set' and description 'Set a project setting in project.godot' indicate modification of project configuration file.
Attacks that exploit this kind of access
The rule that runs project_setting_set 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 project_setting_set, this is the rule to start with:
project_setting_set 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 project_setting_set call is checked against it from then on.
Questions about project_setting_set
Set a project setting in project.godot. 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.
Register the Godot MCP server in PolicyLayer and add a rule for project_setting_set: 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.
project_setting_set 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 project_setting_set 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 project_setting_set. 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.
project_setting_set is provided by the Godot MCP server (chanceflow/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