set_error_handling
Configure how the editor handles errors and warnings during gameplay
This record as markdown: /tools/keeveeg-godot-mcp/set-error-handling.md
What set_error_handling does on Godot
AI agents use set_error_handling 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 |
|---|---|---|---|
break_on_error | boolean | — | Break into debugger on error |
break_on_warning | boolean | — | Break into debugger on warning |
Parameters from the server's own tool schema.
Why set_error_handling is rated Medium
This tool creates or modifies configuration state in the Godot editor (error handling behavior, warning display settings). It does not execute arbitrary code, delete data irreversibly, or move money—it changes settings reversibly. The modification of editor configuration qualifies as Write-category.
From the tool's definition Tool name 'set_error_handling' combined with description 'Configure how the editor handles errors and warnings during gameplay' indicates modification of editor configuration settings.
Attacks that exploit this kind of access
The rule that runs set_error_handling 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_error_handling, this is the rule to start with:
set_error_handling 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_error_handling call is checked against it from then on.
Questions about set_error_handling
Configure how the editor handles errors and warnings during gameplay. 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_error_handling accepts 2 parameters: break_on_error, break_on_warning. 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_error_handling: 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_error_handling 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_error_handling 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_error_handling. 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_error_handling 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