runtime_set_property
Set a property on a live node. DESTRUCTIVE (mutates running game state) — gated by confirmation. Rich types use the {\
This record as markdown: /tools/godot-breakpoint-mcp/runtime-set-property.md
What runtime_set_property does on Godot Breakpoint
AI agents invoke runtime_set_property to trigger actions in Godot Breakpoint. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why runtime_set_property is rated High
This tool modifies the live runtime state of a running game, which is an active system mutation. While labeled 'DESTRUCTIVE' in the description, it does not irreversibly delete or purge data — it mutates in-memory game state that could be reset by restarting the game. This makes it best classified as Execute (triggers external operation with state-dependent effects on a running process).
From the tool's definition Set a property on a live node. DESTRUCTIVE (mutates running game state) — gated by confirmation.
Attacks that exploit this kind of access
The rule that runs runtime_set_property safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runtime_set_property, this is the rule to start with:
runtime_set_property stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every runtime_set_property call is checked against it from then on.
Questions about runtime_set_property
Set a property on a live node. DESTRUCTIVE (mutates running game state) — gated by confirmation. Rich types use the {\. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for runtime_set_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 Breakpoint. Nothing to install.
runtime_set_property is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the runtime_set_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 runtime_set_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.
runtime_set_property is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
Across the catalogue