Run the Godot project and capture output
AI agents invoke run_project to trigger actions in Godot MCP Enhanced. 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 Godot project code, which could perform any operation defined in the project's scripts and scenes (file I/O, network requests, system calls via GDScript, etc.). While not inherently destructive, execution of unknown code poses significant risk if an AI misuses it or the project contains malicious logic.
From the tool's definition Tool name and description explicitly state 'Run the Godot project' - this triggers external execution of game engine code whose effects depend on what the project contains and what it does when run.
Attacks that exploit this kind of access
Run the Godot project and capture output. It is categorised as a Execute tool in the Godot MCP Enhanced MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot MCP Enhanced 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 Enhanced. 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 Enhanced MCP server (xinyuzjj/godot-mcp). 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 →