add_component_with_properties
Add a component to a GameObject and configure its properties in one call (properties PERSIST through save+reload). Use list_available_components to find valid types. Returns appliedProperties + failedProperties so you can see exactly what stuck
This record as markdown: /tools/sbox/add-component-with-properties.md
What add_component_with_properties does on Sbox
AI agents use add_component_with_properties 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_component_with_properties is rated Medium
This tool creates or modifies game object components with persistent effects (save+reload survival). While it modifies game state reversibly (components can be removed), it goes beyond simple data queries into structural game world modification. It does not delete, execute arbitrary code, or move money, so Write is the appropriate category.
From the tool's definition Tool description states 'Add a component to a GameObject and configure its properties in one call' and 'properties PERSIST through save+reload', indicating creation/modification of game object state that is saved permanently.
Attacks that exploit this kind of access
The rule that runs add_component_with_properties 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_component_with_properties, this is the rule to start with:
add_component_with_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 Sbox, apply this rule, and every add_component_with_properties call is checked against it from then on.
Questions about add_component_with_properties
Add a component to a GameObject and configure its properties in one call (properties PERSIST through save+reload). Use list_available_components to find valid types. Returns appliedProperties + failedProperties so you can see exactly what stuck. 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_component_with_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 Sbox. Nothing to install.
add_component_with_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 add_component_with_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 add_component_with_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.
add_component_with_properties 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