update_project_uids · Godot MCP: Risk & Policy

WHAT IT DOES

What update_project_uids does on Godot

AI agents use update_project_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.

PARAMETERS

Parameter	Type	Required	Description
`check_only`	object	—	Only report missing UIDs, do not fix them

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_project_uids needs a policy

This tool modifies project state by scanning and updating UIDs (Unique IDentifiers used by Godot for tracking assets/nodes). While the exact scope is somewhat unclear from the terse description, the word 'update' combined with UID management in a game engine context indicates data modification. This is Write rather than Execute because it performs a structured data update rather than arbitrary code execution.

From the tool's definition Tool name 'update_project_uids' combined with description 'Scan for missing UIDs' indicates modification of project metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_uids Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_project_uids": {
      "limits": [
        {
          "counter": "update_project_uids_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about update_project_uids

What does the update_project_uids tool do? +

Scan for missing UIDs. 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.

What parameters does update_project_uids accept? +

update_project_uids accepts 1 parameter: check_only. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_project_uids? +

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. Nothing to install.

What risk level is update_project_uids? +

update_project_uids is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_project_uids? +

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.

How do I block update_project_uids completely? +

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.

What MCP server provides update_project_uids? +

update_project_uids 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.