AI agents call read_container to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | object | — | Container node name |
scene_path | string | Yes | Path to .tscn scene |
Parameters from the server's own tool schema.
This tool retrieves or queries the layout information of a Container node in Godot without creating, modifying, or deleting any data. It is a pure read operation with no destructive or executable effects, making it low-severity.
From the tool's definition Tool name is 'read_container' and description states 'Read Container layout' — the verb 'read' and absence of modification language clearly indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Read Container layout. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_container accepts 2 parameters: name, scene_path. Required: 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 read_container: 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.
read_container 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 read_container 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 read_container. 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.
read_container 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.
read_container is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →