remove_component
Remove a component from a GameObject by type name (e.g.
This record as markdown: /tools/sbox/remove-component.md
What remove_component does on Sbox
AI agents call remove_component to permanently remove resources in Sbox, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_component is rated Critical
Removing a component from a GameObject is a destructive operation: the component and its configuration are deleted. While the game object itself remains, the component data is lost and cannot be recovered without re-adding and reconfiguring it. The description is partially truncated but the tool name clearly indicates deletion.
From the tool's definition remove_component — removes a component from a GameObject; this is an irreversible deletion of a component by type name
Attacks that exploit this kind of access
The rule that runs remove_component 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 remove_component, this is the rule to start with:
remove_component is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every remove_component call is checked against it from then on.
Questions about remove_component
Remove a component from a GameObject by type name (e.g. It is categorised as a Destructive tool in the Sbox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sbox MCP server in PolicyLayer and add a rule for remove_component: 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.
remove_component is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_component 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 remove_component. 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.
remove_component 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.
Across the catalogue