Run the Godot project and capture output
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.
This tool executes arbitrary code within the Godot project context. While not inherently destructive on its own, running a Godot project can have significant side effects depending on what the project contains (file I/O, network operations, resource modifications, etc.). The blast radius is high because a malicious or buggy project run could consume resources, modify files, or perform unintended actions.
From the tool's definition 'Run the Godot project' - explicitly invokes project execution. Combined with 'capture output', this tool triggers external operations (running a game engine project) whose effects depend on project code arguments.
Documented attack patterns abuse exactly the kind of access run_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_project:
{
"version": "1",
"default": "deny",
"tools": {
"run_project": {
"limits": [
{
"counter": "run_project_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
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 (leesinliang/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Godot MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Godot MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.