This record as markdown: /tools/keeveeg-godot-mcp/set-scene-meta.md
What set_scene_meta does on Godot
AI agents use set_scene_meta 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 |
|---|---|---|---|
key | string | Yes | Metadata key |
value | object | — | Metadata value (string, number, bool, array, or dict) |
scene_path | string | — | Omit or pass empty string — only the current scene is supported |
Parameters from the server's own tool schema.
Why set_scene_meta is rated Medium
This tool creates or modifies metadata on a scene's root node, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). Severity is medium because modifying scene metadata could affect game behavior or project state, but changes are typically reversible through undo or reversion.
From the tool's definition Tool name 'set_scene_meta' and description 'Set metadata on the current scene's root node' indicate modification of scene metadata.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs set_scene_meta 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_meta, this is the rule to start with:
set_scene_meta 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_meta call is checked against it from then on.
Questions about set_scene_meta
Set metadata on the current scene's root node. 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_meta accepts 3 parameters: key, value, scene_path. Required: key. 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_meta: 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_meta 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_meta 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_meta. 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_meta 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