project_update_uids
Update UID references in a Godot project by resaving resources (for Godot 4.4+).
This record as markdown: /tools/chanceflow-godot-mcp/project-update-uids.md
What project_update_uids does on Godot
AI agents use project_update_uids 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.
Why project_update_uids is rated Medium
This tool performs a Write operation: it modifies project resources by resaving them with updated UID references. While the operation affects multiple resources (higher blast radius if misused by an agent that corrupts UIDs), it is not destructive because resaving is reversible and the intent is corrective rather than destructive.
From the tool's definition Tool description states 'Update UID references in a Godot project by resaving resources' — this modifies existing project resources in place. The verb 'update' and 'resaving' indicate reversible modifications to data structures within the project.
Attacks that exploit this kind of access
The rule that runs project_update_uids 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 project_update_uids, this is the rule to start with:
project_update_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every project_update_uids call is checked against it from then on.
Questions about project_update_uids
Update UID references in a Godot project by resaving resources (for Godot 4.4+). 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.
Register the Godot MCP server in PolicyLayer and add a rule for project_update_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. Nothing to install.
project_update_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 project_update_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 project_update_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.
project_update_uids is provided by the Godot MCP server (chanceflow/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