godot_run_project
Run the project (detached). Optionally start from a specific scene path (res://...). Returns the process id.
This record as markdown: /tools/godot-breakpoint-mcp/godot-run-project.md
What godot_run_project does on Godot Breakpoint
AI agents invoke godot_run_project to trigger actions in Godot 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_run_project is rated High
This tool executes external code (the Godot project runtime) whose effects depend entirely on what the project contains. While not inherently destructive or financial, a malicious or compromised project could perform any action the Godot engine permits: file I/O, network access, spawning processes, or hardware control. The 'detached' execution and PID return indicate full subprocess spawning.
From the tool's definition Tool description states 'Run the project (detached)' and 'Returns the process id' — this executes arbitrary Godot project code with full engine capabilities.
Attacks that exploit this kind of access
The rule that runs godot_run_project safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For godot_run_project, this is the rule to start with:
godot_run_project 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 Breakpoint, apply this rule, and every godot_run_project call is checked against it from then on.
Questions about godot_run_project
Run the project (detached). Optionally start from a specific scene path (res://...). Returns the process id. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for godot_run_project: 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 Breakpoint. Nothing to install.
godot_run_project 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_run_project 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_run_project. 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_run_project is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
Across the catalogue