Update UID references in a Godot project by resaving resources (for Godot 4.4+)
AI agents use update_project_uids to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool modifies project metadata (UIDs and resource references) by resaving them. While it is reversible (resources can be restored from version control or backups), it directly alters the internal structure of Godot project files.
From the tool's definition Tool description explicitly states "Update UID references in a Godot project by resaving resources". The verb "Update" and the action of "resaving resources" indicate modification of project data.
Documented attack patterns abuse exactly the kind of access update_project_uids gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for update_project_uids:
{
"version": "1",
"default": "deny",
"tools": {
"update_project_uids": {
"limits": [
{
"counter": "update_project_uids_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_project_uids 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.
Free to start. No card required.
Update UID references in a Godot project by resaving resources (for Godot 4.4+). It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for update_project_uids: 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 Devtool. Nothing to install.
update_project_uids 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 update_project_uids 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 update_project_uids. 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.
update_project_uids is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.