run_project

Run the Godot project and capture output

SERVERGodot MCP SOURCE6ninelives/godot-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/6ninelives-godot-mcp/run-project.md

WHAT IT DOES

What run_project does on Godot MCP

AI agents invoke run_project to trigger actions in Godot MCP. 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.

RISK

Why run_project is rated High

The tool triggers execution of external operations (the Godot game engine and all associated project code) whose effects depend on project contents and state. This is a classic Execute category action rather than Read (no retrieval only), Write (not creating/modifying data reversibly), or Destructive (not deleting).

From the tool's definition Tool name 'run_project' and description 'Run the Godot project and capture output' indicate execution of arbitrary code within the Godot engine environment. Running a project executes all game logic, scripts, and engine initialization code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_project safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot MCP, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_project": {
      "limits": [
        {
          "counter": "run_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot MCP, apply this rule, and every run_project call is checked against it from then on.

FAQ

Questions about run_project

What does the run_project tool do? +

Run the Godot project and capture output. It is categorised as a Execute tool in the Godot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_project? +

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 MCP. Nothing to install.

What risk level is run_project? +

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

Can I rate-limit run_project? +

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.

How do I block run_project completely? +

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.

What MCP server provides run_project? +

run_project is provided by the Godot MCP server (6ninelives/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 18 Godot tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →