set_scene_unique_name
Toggle the unique name flag on a node (accessible as %NodeName)
This record as markdown: /tools/keeveeg-godot-mcp/set-scene-unique-name.md
What set_scene_unique_name does on Godot
AI agents use set_scene_unique_name 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
unique | boolean | — | Enable (true) or disable (false) unique name (default: true) |
node_path | string | Yes | Node path within the scene |
Parameters from the server's own tool schema.
Why set_scene_unique_name is rated Medium
This tool modifies node metadata (the unique name flag) within a Godot scene, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), create financial obligations (Financial), or merely read state (Read).
From the tool's definition Tool description states "Toggle the unique name flag on a node", indicating modification of a node's properties/metadata. The term "toggle" and "flag" confirm state modification rather than retrieval.
Attacks that exploit this kind of access
The rule that runs set_scene_unique_name 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 set_scene_unique_name, this is the rule to start with:
set_scene_unique_name 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 set_scene_unique_name call is checked against it from then on.
Questions about set_scene_unique_name
Toggle the unique name flag on a node (accessible as %NodeName). 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.
set_scene_unique_name accepts 2 parameters: unique, node_path. Required: node_path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for set_scene_unique_name: 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.
set_scene_unique_name 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 set_scene_unique_name 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 set_scene_unique_name. 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.
set_scene_unique_name is provided by the Godot MCP server (@keeveeg/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