resource_set_property
Set a single property on a resource file and save it. DESTRUCTIVE (writes a file) — gated by confirmation. The value uses the tagged-Variant convention.
This record as markdown: /tools/godot-breakpoint-mcp/resource-set-property.md
What resource_set_property does on Godot Breakpoint
AI agents use resource_set_property to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why resource_set_property is rated Medium
While the description labels this as 'DESTRUCTIVE' and it does save files, the core operation is modification (setting a property) rather than irreversible destruction. It is gated by confirmation, further suggesting reversibility through undo or re-setting.
From the tool's definition 'Set a single property on a resource file and save it. DESTRUCTIVE (writes a file)' — the tool modifies and persists a resource file. The description itself uses 'DESTRUCTIVE' but qualifies it as 'writes a file' rather than irreversible deletion/overwrite.
Attacks that exploit this kind of access
The rule that runs resource_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 resource_set_property, this is the rule to start with:
resource_set_property 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every resource_set_property call is checked against it from then on.
Questions about resource_set_property
Set a single property on a resource file and save it. DESTRUCTIVE (writes a file) — gated by confirmation. The value uses the tagged-Variant convention. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for resource_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.
resource_set_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 resource_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 resource_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.
resource_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.
This server
Across the catalogue