This record as markdown: /tools/yanhuifair-godot-mcp/run-project.md
What run_project does on Godot
AI agents invoke run_project 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
debug | object | — | Run with debugger |
scene | object | — | Specific scene to run |
headless | object | — | Run in headless mode (no window) |
window_size | object | — | Window size (e.g. "1280x720", "1920x1080") |
project_path | object | — | Project path (default: current project root; must resolve inside the project root) |
Parameters from the server's own tool schema.
Why run_project is rated High
Runs a Godot project, executing arbitrary code with side effects dependent on project contents.
From the tool's definition Run the Godot project. Executes arbitrary code and external operations.
Attacks that exploit this kind of access
The rule that runs run_project 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 run_project, this is the rule to start with:
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, apply this rule, and every run_project call is checked against it from then on.
Questions about run_project
Run the Godot 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.
run_project accepts 5 parameters: debug, scene, headless, window_size, project_path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for 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. Nothing to install.
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 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 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.
run_project is provided by the Godot MCP server (@yanhuifair/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.
Across the catalogue