This record as markdown: /tools/keeveeg-godot-mcp/set-debug-options.md
What set_debug_options does on Godot
AI agents use set_debug_options 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 |
|---|---|---|---|
optimize | boolean | — | Enable optimizations |
debug_build | boolean | — | Enable debug build (includes symbols) |
release_debug | boolean | — | Release build with debug info |
Parameters from the server's own tool schema.
Why set_debug_options is rated Medium
The tool modifies configuration settings (debug and optimization options) in a Godot project. This is a reversible write operation — settings can be changed back. It does not execute code, delete data, or involve finances. Severity is medium because misconfigured debug/optimization settings could affect build output or runtime behavior.
From the tool's definition Configure debug and optimization options
Attacks that exploit this kind of access
The rule that runs set_debug_options 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 set_debug_options, this is the rule to start with:
set_debug_options 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 set_debug_options call is checked against it from then on.
Questions about set_debug_options
Configure debug and optimization options. 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.
set_debug_options accepts 3 parameters: optimize, debug_build, release_debug. 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 set_debug_options: 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.
set_debug_options 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 set_debug_options 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 set_debug_options. 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.
set_debug_options 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