rigidbody_set_properties
Tune a RigidBody2D/3D in the edited scene (undoable): mass (> 0), gravity_scale, linear_damp, angular_damp. Only the provided properties change. In-scene and undoable — not gated.
This record as markdown: /tools/breakpoint-mcp/rigidbody-set-properties.md
What rigidbody_set_properties does on Breakpoint
AI agents use rigidbody_set_properties 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 |
|---|---|---|---|
mass | number | — | Body mass (> 0) |
path | string | Yes | RigidBody2D/3D node path relative to the scene root |
linear_damp | number | — | Linear damping (≥ 0) |
angular_damp | number | — | Angular damping (≥ 0) |
gravity_scale | number | — | Multiplier on gravity (1 = normal, 0 = float) |
Parameters from the server's own tool schema.
Why rigidbody_set_properties is rated Medium
This tool creates or modifies data (physics properties of RigidBody objects) in a reversible manner—the description emphasizes it is 'undoable', making it a Write action rather than Destructive.
From the tool's definition Tool description explicitly states it "Tune[s] a RigidBody2D/3D" and modifies properties like "mass", "gravity_scale", "linear_damp", "angular_damp". It is marked as "undoable" and "In-scene", indicating reversible modifications to game object properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs rigidbody_set_properties 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 rigidbody_set_properties, this is the rule to start with:
rigidbody_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every rigidbody_set_properties call is checked against it from then on.
Questions about rigidbody_set_properties
Tune a RigidBody2D/3D in the edited scene (undoable): mass (> 0), gravity_scale, linear_damp, angular_damp. Only the provided properties change. In-scene and undoable — not gated. 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.
rigidbody_set_properties accepts 5 parameters: mass, path, linear_damp, angular_damp, gravity_scale. Required: path. 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 rigidbody_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 Breakpoint. Nothing to install.
rigidbody_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 rigidbody_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 rigidbody_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.
rigidbody_set_properties 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