Set a property value on a node in the currently open scene.
AI agents use update_property to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
This tool creates or modifies game object properties reversibly within an open scene. It does not execute arbitrary code, delete data, or affect financial systems. However, it carries medium severity because inadvertent property modifications could alter game behavior, break scenes, or corrupt gameplay logic if misused by an AI agent without proper guardrails.
From the tool's definition Tool name 'update_property' and description 'Set a property value on a node' indicate modification of existing data within the Godot scene.
Attacks that exploit this kind of access
Set a property value on a node in the currently open scene. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for update_property: 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 MCP Server. Nothing to install.
update_property 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 update_property 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 update_property. 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.
update_property is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →