editor_run_gdscript · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_run_gdscript does on Godot

AI agents invoke editor_run_gdscript 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.

PARAMETERS

Parameter	Type	Required	Description
`code`	string	Yes	GDScript code to execute in editor context

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_run_gdscript needs a policy

This tool allows unrestricted execution of GDScript (Godot's scripting language) within the editor context. While GDScript execution in Godot is generally constrained by the engine's sandbox, 'arbitrary' code execution in an editor context can access scene graphs, project files, and editor state.

From the tool's definition 'Execute arbitrary GDScript code in editor context' — the tool explicitly permits running arbitrary code in the editor's runtime environment.

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_run_gdscript Rate-limited

editor_run_gdscript 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_run_gdscript": {
      "limits": [
        {
          "counter": "editor_run_gdscript_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about editor_run_gdscript

What does the editor_run_gdscript tool do? +

Execute arbitrary GDScript code in editor context. 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.

What parameters does editor_run_gdscript accept? +

editor_run_gdscript accepts 1 parameter: code. Required: code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_run_gdscript? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_run_gdscript: 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.

What risk level is editor_run_gdscript? +

editor_run_gdscript is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit editor_run_gdscript? +

Yes. Add a rate_limit block to the editor_run_gdscript 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.

How do I block editor_run_gdscript completely? +

Set action: deny in the PolicyLayer policy for editor_run_gdscript. 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.

What MCP server provides editor_run_gdscript? +

editor_run_gdscript is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.