create_export_preset
Create an export preset in export_presets.cfg (Windows Desktop/Linux/macOS/Android/iOS/Web).
This record as markdown: /tools/yanhuifair-godot-mcp/create-export-preset.md
What create_export_preset does on Godot
AI agents use create_export_preset to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Preset name, e.g. "Windows Release" |
options | object | — | Extra [preset.N.options] keys, e.g. {"binary_format/embed_pck":"true"} |
platform | string | Yes | Godot export platform name (must match the engine exactly) |
runnable | object | — | Mark this preset as the runnable one for its platform |
export_path | object | — | Output path, e.g. "build/game.exe". Defaults to build/<name><platform extension>. |
export_filter | object | — | Which resources to include |
exclude_filter | object | — | Comma-separated exclude globs |
include_filter | object | — | Comma-separated include globs, e.g. "*.json,*.txt" |
custom_features | object | — | Comma-separated custom feature tags |
dedicated_server | object | — | Export as a dedicated server build |
Parameters from the server's own tool schema.
Why create_export_preset is rated Medium
Creates or modifies export configuration files reversibly; changes are editable and not destructive.
From the tool's definition Create an export preset in export_presets.cfg
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs create_export_preset 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 create_export_preset, this is the rule to start with:
create_export_preset stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 create_export_preset call is checked against it from then on.
Questions about create_export_preset
Create an export preset in export_presets.cfg (Windows Desktop/Linux/macOS/Android/iOS/Web). It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_export_preset accepts 10 parameters: name, options, platform, runnable, export_path, export_filter, exclude_filter, include_filter, custom_features, dedicated_server. Required: name, 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 create_export_preset: 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.
create_export_preset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_export_preset 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 create_export_preset. 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.
create_export_preset is provided by the Godot MCP server (@yanhuifair/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.
This server
Across the catalogue