Read Inspector properties from the selected or addressed node through the live editor bridge
AI agents call editor_inspector_get_properties to retrieve information from Godot Devtool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves property metadata from a Godot editor node via the live bridge, matching the Read category definition (retrieves or queries data; no side effects). The live editor bridge provides introspection of runtime state without executing code, modifying data, or triggering external operations. Severity is low because misuse only exposes existing project metadata, not destructive or execution capabilities.
From the tool's definition Tool name and description explicitly state 'Read Inspector properties' with no modification capability. The verb 'get' and passive 'read' confirm data retrieval only. No side effects or mutations are indicated.
Documented attack patterns abuse exactly the kind of access editor_inspector_get_properties gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for editor_inspector_get_properties:
{
"version": "1",
"default": "deny",
"tools": {
"editor_inspector_get_properties": {}
}
}editor_inspector_get_properties is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read Inspector properties from the selected or addressed node through the live editor bridge. It is categorised as a Read tool in the Godot Devtool MCP Server, which means it retrieves data without modifying state.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for editor_inspector_get_properties: 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 Devtool. Nothing to install.
editor_inspector_get_properties 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 editor_inspector_get_properties 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 editor_inspector_get_properties. 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.
editor_inspector_get_properties is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.