This record as markdown: /tools/keeveeg-godot-mcp/get-scene-meta.md
What get_scene_meta does on Godot
AI agents call get_scene_meta to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scene_path | string | — | Scene file path (empty for current scene) |
Parameters from the server's own tool schema.
Why get_scene_meta is rated Low
This tool retrieves metadata from a scene node without creating, modifying, deleting, or executing anything. It is a straightforward read operation. The blast radius is minimal since it only accesses existing metadata without triggering any external operations or altering state.
From the tool's definition Tool name is 'get_scene_meta' and description states 'Get metadata stored on a scene's root node' — this is a retrieval operation with no modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_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 get_scene_meta, this is the rule to start with:
get_scene_meta is read-only, so it stays allowed. 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 get_scene_meta call is checked against it from then on.
Questions about get_scene_meta
Get metadata stored on a scene's root node. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_scene_meta accepts 1 parameter: scene_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 get_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.
get_scene_meta is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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