AI agents call read_multimesh 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 |
|---|---|---|---|
scene_path | object | — | Filter to scene |
Parameters from the server's own tool schema.
This tool retrieves and lists MultiMeshInstance nodes within the Godot engine, which is a read-only operation. It queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent could only gain visibility into scene structure.
From the tool's definition Tool name 'read_multimesh' and description 'List MultiMeshInstance nodes' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List MultiMeshInstance nodes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_multimesh 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 read_multimesh: 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_multimesh 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_multimesh 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_multimesh. 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_multimesh 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_multimesh 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 →