launch_editor · Godot MCP Unified MCP: Risk & Policy

WHAT IT DOES

What launch_editor does on Godot MCP Unified

AI agents invoke launch_editor to trigger actions in Godot MCP Unified. 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 launch_editor needs a policy

Launching an external application like Godot editor constitutes execution of code and triggers external operations whose effects depend on runtime arguments (project path, editor configuration). While the immediate action is to start a process rather than run arbitrary code directly, the editor itself becomes a gateway to extensive destructive and write operations on the project.

From the tool's definition The tool 'launch_editor' launches the Godot editor, which initiates an external application/process with full capabilities to modify game assets, scripts, scenes, and project files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

launch_editor Rate-limited

launch_editor 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": {
    "launch_editor": {
      "limits": [
        {
          "counter": "launch_editor_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 Unified, so you can run agents against it safely.

FAQ

Questions about launch_editor

What does the launch_editor tool do? +

Launch Godot editor for a specific project. It is categorised as a Execute tool in the Godot MCP Unified MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on launch_editor? +

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

What risk level is launch_editor? +

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

Can I rate-limit launch_editor? +

Yes. Add a rate_limit block to the launch_editor 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 launch_editor completely? +

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

launch_editor is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.