project_set_setting
Write a ProjectSettings value. Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation.
This record as markdown: /tools/godot-breakpoint-mcp/project-set-setting.md
What project_set_setting does on Godot Breakpoint
AI agents use project_set_setting to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why project_set_setting is rated Medium
This tool modifies project settings and can persist changes to disk. Although the description uses 'DESTRUCTIVE' language, the core action is writing/updating configuration data (reversible through re-setting the value), not permanently deleting or purifying data. It belongs in Write category rather than Destructive because the changes can be undone by setting the value back.
From the tool's definition Tool description states 'Write a ProjectSettings value' and explicitly mentions ability to 'persist to project.godot' when save=true. While labeled 'DESTRUCTIVE', the actual mechanism is overwriting configuration settings rather than irreversible deletion.
Attacks that exploit this kind of access
The rule that runs project_set_setting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_set_setting, this is the rule to start with:
project_set_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 Breakpoint, apply this rule, and every project_set_setting call is checked against it from then on.
Questions about project_set_setting
Write a ProjectSettings value. Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for project_set_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 Breakpoint. Nothing to install.
project_set_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 project_set_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 project_set_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.
project_set_setting is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue