set_texture_import_flags
Set import flags (compress, mipmaps, etc.) in a .import config.
This record as markdown: /tools/yanhuifair-godot-mcp/set-texture-import-flags.md
What set_texture_import_flags does on Godot
AI agents use set_texture_import_flags 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 |
|---|---|---|---|
path | string | Yes | Image asset path (e.g. "sprites/hero.png"); modifies its .import config |
flags | object | Yes | Import params to set, e.g. {"compress/mode": "2", "process/size_limit": "512"} |
Parameters from the server's own tool schema.
Why set_texture_import_flags is rated Medium
Modifies texture import configuration settings, affecting asset processing but not deleting or executing code.
From the tool's definition Set import flags in .import config
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_texture_import_flags 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 set_texture_import_flags, this is the rule to start with:
set_texture_import_flags 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 set_texture_import_flags call is checked against it from then on.
Questions about set_texture_import_flags
Set import flags (compress, mipmaps, etc.) in a .import config. 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.
set_texture_import_flags accepts 2 parameters: path, flags. Required: path, flags. 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 set_texture_import_flags: 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.
set_texture_import_flags 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 set_texture_import_flags 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 set_texture_import_flags. 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.
set_texture_import_flags 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