grid_duplicate
Clone a GameObject into an X/Y/Z grid with fixed spacing (the original stays in place). Each count is clamped to 50 and total clones to 500. Great for fences, crates, pillars, foliage rows.
This record as markdown: /tools/sbox/grid-duplicate.md
What grid_duplicate does on Sbox
AI agents use grid_duplicate 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 grid_duplicate is rated Medium
This tool creates and modifies game objects by duplicating them in a grid pattern. While the operation is reversible (objects can be deleted), it creates new data structures in the game world. The clamps on count and total clones limit the blast radius, preventing unbounded resource consumption. This fits Write category (creates/modifies data reversibly) rather than Destructive (which would be irreversible).
From the tool's definition Tool description states it will 'Clone a GameObject into an X/Y/Z grid' and 'Each count is clamped to 50 and total clones to 500', indicating creation of multiple new objects in the game scene.
Attacks that exploit this kind of access
The rule that runs grid_duplicate 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 grid_duplicate, this is the rule to start with:
grid_duplicate 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 grid_duplicate call is checked against it from then on.
Questions about grid_duplicate
Clone a GameObject into an X/Y/Z grid with fixed spacing (the original stays in place). Each count is clamped to 50 and total clones to 500. Great for fences, crates, pillars, foliage rows. 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 grid_duplicate: 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.
grid_duplicate 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 grid_duplicate 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 grid_duplicate. 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.
grid_duplicate 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