Write Inspector properties on the selected or addressed node through the live editor bridge
AI agents use editor_inspector_set_properties to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
This tool creates or modifies data (node properties) reversibly through the editor interface. While it affects a live project, the changes are not inherently destructive—properties can be reverted or undone.
From the tool's definition Tool description explicitly states 'Write Inspector properties' and operates on a live editor bridge, indicating it modifies node configuration in the Godot editor at runtime.
Documented attack patterns abuse exactly the kind of access editor_inspector_set_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_set_properties:
{
"version": "1",
"default": "deny",
"tools": {
"editor_inspector_set_properties": {
"limits": [
{
"counter": "editor_inspector_set_properties_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}editor_inspector_set_properties 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.
Free to start. No card required.
Write Inspector properties on the selected or addressed node through the live editor bridge. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for editor_inspector_set_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_set_properties 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 editor_inspector_set_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_set_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_set_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.