Run a Godot project in debug mode (background). Optionally run a specific scene.
AI agents invoke run_project to trigger actions in Godot Mcp Pilot. 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.
This tool executes arbitrary game code defined in a Godot project. While not destructive by itself, it has a high blast radius because a malicious or compromised project could perform harmful operations (file I/O, network access, system calls via GDScript). An AI agent with this capability could inadvertently launch and execute untrusted game logic.
From the tool's definition Tool description states 'Run a Godot project in debug mode (background)'. The verb 'run' combined with launching a game project constitutes executing code whose effects depend on what the project contains and does.
Attacks that exploit this kind of access
Run a Godot project in debug mode (background). Optionally run a specific scene. It is categorised as a Execute tool in the Godot Mcp Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Mcp Pilot 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 Pilot. 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 Pilot MCP server (pushks18/godot-mcp-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →