run_editor_script · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_editor_script does on Godot MCP Server

AI agents invoke run_editor_script to trigger actions in Godot MCP Server. 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.

WHY IT NEEDS A POLICY

Why run_editor_script needs a policy

This tool runs code in the Godot editor context with no constraints on what GDScript can accomplish. An AI agent could use this to modify game files, delete assets, alter project settings, inject malicious code into scenes, or perform any action the editor permits. While not strictly destructive by itself, arbitrary code execution is the highest-risk capability in security contexts.

From the tool's definition Tool description states 'Execute arbitrary GDScript code in the editor context (EditorScript)'. The verb 'Execute' combined with 'arbitrary' code is unambiguous.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_editor_script Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_editor_script": {
      "limits": [
        {
          "counter": "run_editor_script_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about run_editor_script

What does the run_editor_script tool do? +

Execute arbitrary GDScript code in the editor context (EditorScript). It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_editor_script? +

Register the Godot MCP Server MCP server in PolicyLayer and add a rule for run_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 MCP Server. Nothing to install.

What risk level is run_editor_script? +

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

Can I rate-limit run_editor_script? +

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

How do I block run_editor_script completely? +

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

What MCP server provides run_editor_script? +

run_editor_script is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.