execute_editor_script
Execute a GDScript snippet in the editor context (EditorScript)
This record as markdown: /tools/keeveeg-godot-mcp/execute-editor-script.md
What execute_editor_script does on Godot
AI agents invoke execute_editor_script to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | GDScript code to execute |
Parameters from the server's own tool schema.
Why execute_editor_script is rated High
This tool allows arbitrary code execution in the Godot editor environment via GDScript. While not as severe as destructive operations, code execution poses high risk because an AI agent could run malicious scripts that modify project files, corrupt assets, or compromise the development environment.
From the tool's definition Tool description states 'Execute a GDScript snippet in the editor context (EditorScript)' — this directly executes code.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs execute_editor_script 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 execute_editor_script, this is the rule to start with:
execute_editor_script stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 execute_editor_script call is checked against it from then on.
Questions about execute_editor_script
Execute a GDScript snippet in the editor context (EditorScript). It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
execute_editor_script accepts 1 parameter: code. Required: code. 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 execute_editor_script: 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.
execute_editor_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_editor_script 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 execute_editor_script. 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.
execute_editor_script 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.
Across the catalogue