update_export_preset
Update fields/options of an existing export preset (by name or index).
This record as markdown: /tools/yanhuifair-godot-mcp/update-export-preset.md
What update_export_preset does on Godot
AI agents use update_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 |
|---|---|---|---|
fields | object | — | Raw [preset.N] keys to set, e.g. {"seed":"12345"} |
preset | string | Yes | Preset name or zero-based index |
options | object | — | Raw [preset.N.options] keys to set, e.g. {"texture_format/s3tc_bptc":"true"} |
runnable | object | — | Mark/unmark as the runnable preset for its platform |
export_path | object | — | New output path |
export_filter | object | — | |
exclude_filter | object | — | |
include_filter | object | — | |
custom_features | object | — | |
dedicated_server | object | — |
Parameters from the server's own tool schema.
Why update_export_preset is rated Medium
Modifies export preset configuration reversibly; affects build outputs but does not delete or execute code directly.
From the tool's definition Update fields/options of an existing export preset
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_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 update_export_preset, this is the rule to start with:
update_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 update_export_preset call is checked against it from then on.
Questions about update_export_preset
Update fields/options of an existing export preset (by name or index). 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.
update_export_preset accepts 10 parameters: fields, preset, options, runnable, export_path, export_filter, exclude_filter, include_filter, custom_features, dedicated_server. 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 update_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.
update_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 update_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 update_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.
update_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