add_joint
Add a physics joint/constraint between two GameObjects. Supports fixed, spring, and slider joint types
This record as markdown: /tools/sbox/add-joint.md
What add_joint does on Sbox
AI agents use add_joint to create or update resources in Sbox, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sbox environment.
Why add_joint is rated Medium
The tool adds (creates) a new physics joint configuration between game objects, which is a reversible modification to the game state. This fits the Write category (creates or modifies data reversibly). Severity is medium because misuse could create unintended physics constraints that break game functionality, but these are reversible by removing the joint.
From the tool's definition Tool description states 'Add a physics joint/constraint between two GameObjects' — this creates a new physics relationship in the game scene that modifies the world state reversibly.
Attacks that exploit this kind of access
The rule that runs add_joint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_joint, this is the rule to start with:
add_joint 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 Sbox, apply this rule, and every add_joint call is checked against it from then on.
Questions about add_joint
Add a physics joint/constraint between two GameObjects. Supports fixed, spring, and slider joint types. It is categorised as a Write tool in the Sbox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sbox MCP server in PolicyLayer and add a rule for add_joint: 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 Sbox. Nothing to install.
add_joint 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 add_joint 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 add_joint. 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.
add_joint is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue