run_exported_build
Run an exported build and capture its output
This record as markdown: /tools/keeveeg-godot-mcp/run-exported-build.md
What run_exported_build does on Godot
AI agents invoke run_exported_build 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 |
|---|---|---|---|
args | array | — | Command-line arguments for the build |
path | string | Yes | Path to the exported executable |
Parameters from the server's own tool schema.
Why run_exported_build is rated High
This tool executes an external process (a Godot exported build), which is a form of code execution. The blast radius is high because a malicious build or unexpected execution could have side effects on the system, consume resources, or perform unintended actions.
From the tool's definition Tool name is 'run_exported_build' and description states 'Run an exported build and capture its output'. This directly executes code/processes whose behavior depends on the build contents and arguments passed.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs run_exported_build 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_exported_build, this is the rule to start with:
run_exported_build 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_exported_build call is checked against it from then on.
Questions about run_exported_build
Run an exported build and capture its output. 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_exported_build accepts 2 parameters: args, path. Required: 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_exported_build: 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_exported_build 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_exported_build 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_exported_build. 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_exported_build is provided by the Godot MCP server (@keeveeg/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