node_set_property
Set a property on a node (undoable). Rich types use the {"__type__":"Vector3","x":..} convention. Example value for position: {"__type__":"Vector3","x":1,"y":0,"z":2}.
This record as markdown: /tools/breakpoint-mcp/node-set-property.md
What node_set_property does on Breakpoint
AI agents use node_set_property to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path relative to the scene root |
value | object | — | New value (JSON scalar, array, object, or a __type__-tagged Variant) |
property | string | Yes | Property name, e.g. position, modulate, text |
Parameters from the server's own tool schema.
Why node_set_property is rated Medium
This tool modifies properties on nodes (e.g., position, rotation, scale) but the change is explicitly undoable/reversible, making it a Write operation rather than Destructive. The blast radius is medium because inappropriate property changes could corrupt scene state or break animations/objects, but the undoable nature and lack of deletion capability limit severity.
From the tool's definition Set a property on a node (undoable). The tool creates or modifies node properties reversibly, as indicated by the 'undoable' note in the description.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_set_property safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_set_property, this is the rule to start with:
node_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 Breakpoint, apply this rule, and every node_set_property call is checked against it from then on.
Questions about node_set_property
Set a property on a node (undoable). Rich types use the {"__type__":"Vector3","x":..} convention. Example value for position: {"__type__":"Vector3","x":1,"y":0,"z":2}. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
node_set_property accepts 3 parameters: path, value, property. Required: path, property. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for node_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 Breakpoint. Nothing to install.
node_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 node_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 node_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.
node_set_property is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue