godot_launch_editor
Open the Godot editor for the configured project (detached). Needed before any editor_* bridge tool can be used.
This record as markdown: /tools/breakpoint-mcp/godot-launch-editor.md
What godot_launch_editor does on Breakpoint
AI agents invoke godot_launch_editor to trigger actions in Breakpoint. 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 godot_launch_editor is rated High
This tool executes an external application (Godot editor) whose effects depend on subsequent user/agent actions within that editor. While launching an editor itself is not immediately destructive, it enables arbitrary operations within Godot's development environment and is a prerequisite for other editor bridge tools.
From the tool's definition The tool 'godot_launch_editor' opens the Godot editor application as a detached process. The verb 'launch' indicates execution of an external application/process.
Attacks that exploit this kind of access
The rule that runs godot_launch_editor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For godot_launch_editor, this is the rule to start with:
godot_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every godot_launch_editor call is checked against it from then on.
Questions about godot_launch_editor
Open the Godot editor for the configured project (detached). Needed before any editor_* bridge tool can be used. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Breakpoint MCP server in PolicyLayer and add a rule for godot_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 Breakpoint. Nothing to install.
godot_launch_editor 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 godot_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.
Set action: deny in the PolicyLayer policy for godot_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.
godot_launch_editor is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue