update_project_uids
Update UID references in a Godot project by resaving resources (for Godot 4.4+)
This record as markdown: /tools/6ninelives-godot-mcp/update-project-uids.md
What update_project_uids does on Godot MCP
AI agents use update_project_uids to create or update resources in Godot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP environment.
Why update_project_uids is rated Medium
The tool updates and rewrites resource UIDs in a Godot project, which constitutes data modification. While the operation could theoretically corrupt UIDs if misapplied (making it potentially destructive), the stated purpose is to update references during a normal maintenance operation (resaving resources). This is reversible via version control, distinguishing it from Destructive category.
From the tool's definition Tool description states 'Update UID references in a Godot project by resaving resources' — this modifies project files (UIDs) through a resave operation, which is reversible through version control or undoing the resave.
Attacks that exploit this kind of access
The rule that runs update_project_uids safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_project_uids, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot MCP, apply this rule, and every update_project_uids call is checked against it from then on.
Questions about update_project_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 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 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 MCP. 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 MCP server (6ninelives/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