This record as markdown: /tools/yanhuifair-godot-mcp/write-import-config.md
What write_import_config does on Godot
AI agents use write_import_config 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 |
|---|---|---|---|
settings | object | Yes | Import settings to write (key=value in the [params] section) |
asset_path | string | Yes | Path to the source asset file |
Parameters from the server's own tool schema.
Why write_import_config is rated Medium
This tool modifies import configuration, which affects how Godot processes assets. While reversible (settings can be re-written), misconfigured import settings could break asset pipelines, cause rendering issues, or affect game functionality. Classified as Write rather than Execute because it directly modifies configuration state without executing arbitrary code.
From the tool's definition Tool name 'write_import_config' and description 'Write import settings' explicitly indicate data modification. The verb 'write' coupled with 'import settings' suggests creating or modifying configuration files related to asset/resource imports in Godot.
Attacks that exploit this kind of access
The rule that runs write_import_config 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 write_import_config, this is the rule to start with:
write_import_config 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 write_import_config call is checked against it from then on.
Questions about write_import_config
Write import 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.
write_import_config accepts 2 parameters: settings, asset_path. Required: settings, asset_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 write_import_config: 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.
write_import_config 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 write_import_config 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 write_import_config. 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.
write_import_config 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