This record as markdown: /tools/keeveeg-godot-mcp/export-for-platform.md
What export_for_platform does on Godot
AI agents invoke export_for_platform 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) |
platform | string | Yes | Target platform |
Parameters from the server's own tool schema.
Why export_for_platform is rated High
Exporting a project triggers a build/compile pipeline and writes output artifacts to disk. This is an external operation that executes the Godot export process, potentially invoking scripts, compiling code, and writing files. It goes beyond a simple write (it runs a process), so Execute is the most appropriate category. Misuse could trigger unintended builds, expose project data, or produce malicious exports.
From the tool's definition Export the project for a specific platform
Attacks that exploit this kind of access
The rule that runs export_for_platform 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_for_platform, this is the rule to start with:
export_for_platform 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_for_platform call is checked against it from then on.
Questions about export_for_platform
Export the project for a specific platform. 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_for_platform accepts 2 parameters: debug, platform. Required: platform. 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_for_platform: 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_for_platform 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_for_platform 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_for_platform. 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_for_platform 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