editor_launch
Launch the Godot editor for a specific project.
This record as markdown: /tools/chanceflow-godot-mcp/editor-launch.md
What editor_launch does on Godot
AI agents invoke editor_launch 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.
Why editor_launch is rated High
Launching the Godot editor is an Execute action because it triggers an external operation (starting the editor process). While not inherently destructive, an AI agent with access to this tool could launch the editor on a project it modifies, potentially causing unintended side effects.
From the tool's definition Tool description states 'Launch the Godot editor for a specific project' — this is launching an external application/process, which is execution of a program whose effects depend on the project argument and editor state.
Attacks that exploit this kind of access
The rule that runs editor_launch 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 editor_launch, this is the rule to start with:
editor_launch 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 editor_launch call is checked against it from then on.
Questions about editor_launch
Launch the Godot editor for a specific project. 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.
Register the Godot MCP server in PolicyLayer and add a rule for editor_launch: 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.
editor_launch 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 editor_launch 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 editor_launch. 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.
editor_launch is provided by the Godot MCP server (chanceflow/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