This record as markdown: /tools/yanhuifair-godot-mcp/editor-reimport-asset.md
What editor_reimport_asset does on Godot
AI agents invoke editor_reimport_asset 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 |
|---|---|---|---|
path | string | Yes |
Parameters from the server's own tool schema.
Why editor_reimport_asset is rated High
Reimporting an asset triggers the Godot editor's import pipeline, which is an active operation with side effects (regenerating import files, updating internal representations). It is not a simple read, nor does it delete data permanently, but it executes an asset processing operation. Misuse could corrupt or overwrite imported asset data unexpectedly, hence medium severity.
From the tool's definition 'Force reimport of an asset' — triggers an external operation (reimport pipeline) on an asset file
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs editor_reimport_asset 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 editor_reimport_asset, this is the rule to start with:
editor_reimport_asset 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 editor_reimport_asset call is checked against it from then on.
Questions about editor_reimport_asset
Force reimport of an asset. 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.
editor_reimport_asset accepts 1 parameter: path. Required: path. 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 editor_reimport_asset: 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.
editor_reimport_asset 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 editor_reimport_asset 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 editor_reimport_asset. 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.
editor_reimport_asset 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.
Across the catalogue