AI agents use write_resource 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 | Path to .tres file (relative to project root) |
properties | object | Yes | Properties to set/overwrite in the [resource] section |
create_backup | object | — | Create .bak backup (default: true) |
Parameters from the server's own tool schema.
This tool modifies resource properties in Godot, which are persistent game assets (scenes, scripts, textures, etc.). While reversible via undo or version control, unauthorized writes to game resources could corrupt project state, break game logic, or inject malicious content into assets. The high severity reflects that resource corruption could require significant remediation.
From the tool's definition Tool name is 'write_resource' and description states 'Write properties to a resource.' The verb 'write' and explicit 'Write properties' indicate data modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Write properties to a resource. 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_resource accepts 3 parameters: path, properties, create_backup. Required: path, properties. 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_resource: 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_resource 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_resource 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_resource. 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_resource 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.
write_resource is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →