This record as markdown: /tools/keeveeg-godot-mcp/export-project.md
What export_project does on Godot
AI agents invoke export_project 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 |
|---|---|---|---|
debug | boolean | — | Export as debug build (default: false = release) |
preset | string | Yes | Export preset name |
pack_only | boolean | — | Export as pack file only (default: false) |
output_path | string | — | Output path for the export |
Parameters from the server's own tool schema.
Why export_project is rated High
Exporting a project is an execution-level operation that runs the Godot build/export pipeline, producing output files. It is not a simple read or write — it triggers external compilation and packaging processes. Misuse could overwrite export artifacts or trigger unintended builds, warranting high severity.
From the tool's definition 'Export the project using a specific preset' — triggers an export operation that compiles/builds project files
Attacks that exploit this kind of access
The rule that runs export_project 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 export_project, this is the rule to start with:
export_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every export_project call is checked against it from then on.
Questions about export_project
Export the project using a specific preset. 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.
export_project accepts 4 parameters: debug, preset, pack_only, output_path. Required: preset. 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 export_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. Nothing to install.
export_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 export_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 export_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.
export_project 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