This record as markdown: /tools/keeveeg-godot-mcp/delete-export-preset.md
What delete_export_preset does on Godot
AI agents call delete_export_preset to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name of the export preset to delete |
Parameters from the server's own tool schema.
Why delete_export_preset is rated Critical
The tool performs a deletion operation that cannot be undone. Export presets are project configuration assets used to build and package games. Deleting a preset destroys that configuration permanently. This qualifies as Destructive rather than Write, as the action is irreversible.
From the tool's definition Tool name and description: 'Delete an export preset from the project' — this irreversibly removes configuration data (an export preset) from a Godot project.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_export_preset, this is the rule to start with:
delete_export_preset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every delete_export_preset call is checked against it from then on.
Questions about delete_export_preset
Delete an export preset from the project. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_export_preset accepts 1 parameter: name. Required: name. 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 delete_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.
delete_export_preset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue