update_project_uids · Godot Mcp Pilot MCP: Risk & Policy

WHAT IT DOES

What update_project_uids does on Godot Mcp Pilot

AI agents invoke update_project_uids to trigger actions in Godot Mcp Pilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why update_project_uids needs a policy

This tool executes an external process (Godot in headless mode) to re-import all project assets. It triggers an external operation with side effects (modifying UID metadata for all assets), but is generally reversible via version control. It doesn't delete or overwrite user data destructively, but does run an external program whose effects depend on the project state, placing it firmly in the Execute category.

From the tool's definition 'Re-import all project assets to refresh Godot 4 UIDs. Runs Godot headlessly.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_uids Rate-limited

update_project_uids stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Mcp Pilot, so you can run agents against it safely.

FAQ

Questions about update_project_uids

What does the update_project_uids tool do? +

Re-import all project assets to refresh Godot 4 UIDs. Runs Godot headlessly. It is categorised as a Execute tool in the Godot Mcp Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on update_project_uids? +

Register the Godot Mcp Pilot 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 Pilot. Nothing to install.

What risk level is update_project_uids? +

update_project_uids is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

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 Pilot MCP server (pushks18/godot-mcp-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.