create_prefab
Save an existing GameObject as a reusable .prefab file. The prefab can be instantiated later
This record as markdown: /tools/sbox/create-prefab.md
What create_prefab does on Sbox
AI agents use create_prefab 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 create_prefab is rated Medium
This tool creates and persists new files (.prefab files) in the game engine's file system. While reversible (prefab files can be deleted or overwritten), it modifies the project state irreversibly in the sense that once saved, the prefab exists as a new artifact. This is a Write operation rather than Destructive because the action itself is not an erasure—it's asset creation.
From the tool's definition The tool description explicitly states it saves a GameObject as a .prefab file, which is a file creation/write operation. The phrase 'Save an existing GameObject as a reusable .prefab file' indicates persistent data modification.
Attacks that exploit this kind of access
The rule that runs create_prefab 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 create_prefab, this is the rule to start with:
create_prefab 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 create_prefab call is checked against it from then on.
Questions about create_prefab
Save an existing GameObject as a reusable .prefab file. The prefab can be instantiated later. 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 create_prefab: 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.
create_prefab 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 create_prefab 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 create_prefab. 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.
create_prefab 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