create_platform_export_preset
Create a new export preset for a specific platform with optional custom settings
This record as markdown: /tools/keeveeg-godot-mcp/create-platform-export-preset.md
What create_platform_export_preset does on Godot
AI agents use create_platform_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 |
platform | string | Yes | Target platform (e.g. 'Windows Desktop', 'Linux', 'Android', 'Web') |
settings | object | — | Optional property key-value pairs |
Parameters from the server's own tool schema.
Why create_platform_export_preset is rated Medium
This tool creates (Write category) a new export preset, which modifies the project configuration state. It is reversible (presets can be deleted or modified), so it does not qualify as Destructive. The severity is medium because misconfiguration could affect build outputs or deployment processes, but the impact is limited to preset configuration without direct code execution or data destruction.
From the tool's definition Tool name 'create_platform_export_preset' and description 'Create a new export preset for a specific platform with optional custom settings' indicate creation of configuration data.
Attacks that exploit this kind of access
The rule that runs create_platform_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_platform_export_preset, this is the rule to start with:
create_platform_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_platform_export_preset call is checked against it from then on.
Questions about create_platform_export_preset
Create a new export preset for a specific platform with optional custom settings. 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_platform_export_preset accepts 3 parameters: name, platform, settings. 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_platform_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_platform_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_platform_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_platform_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_platform_export_preset 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.
This server
Across the catalogue