joint_create
Add a physics joint node under a parent in the edited scene (undoable). 2D types: pin | groove | spring (PinJoint2D/GrooveJoint2D/DampedSpringJoint2D); 3D types: pin | hinge | slider | cone_twist | generic6dof (PinJoint3D/HingeJoint3D/SliderJoint3D/ConeTwistJoint3D/Generic6DOFJoint3D). Optionally...
This record as markdown: /tools/godot-breakpoint-mcp/joint-create.md
What joint_create does on Godot Breakpoint
AI agents use joint_create 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 joint_create is rated Medium
The tool creates new physics joint nodes in a scene, which is a modification operation (Write category). It is explicitly marked as 'undoable', meaning changes can be reverted, making it reversible rather than destructive. Severity is medium because while it modifies the scene structure, the effect is limited to adding a joint node within the editor context and can be undone.
From the tool's definition Tool description states it will 'Add a physics joint node under a parent in the edited scene' and specifies it is 'undoable'. This is a reversible creation/modification operation within the Godot editor scene.
Attacks that exploit this kind of access
The rule that runs joint_create 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 joint_create, this is the rule to start with:
joint_create 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 joint_create call is checked against it from then on.
Questions about joint_create
Add a physics joint node under a parent in the edited scene (undoable). 2D types: pin | groove | spring (PinJoint2D/GrooveJoint2D/DampedSpringJoint2D); 3D types: pin | hinge | slider | cone_twist | generic6dof (PinJoint3D/HingeJoint3D/SliderJoint3D/ConeTwistJoint3D/Generic6DOFJoint3D). Optionally wire node_a/node_b to the two bodies. In-scene and undoable — not gated. 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 joint_create: 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.
joint_create 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 joint_create 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 joint_create. 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.
joint_create 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