commit_placement_plan
Commit a dry-run plan returned by place_along_path, grid_duplicate, or scatter_props. Plans are scene-scoped, capped, and expire after 10 minutes. Success consumes the plan; a complete rollback restores it for retry. The stored transforms are applied without rerolling randomness or repeating grou...
This record as markdown: /tools/sbox/commit-placement-plan.md
What commit_placement_plan does on Sbox
AI agents use commit_placement_plan 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 commit_placement_plan is rated Medium
Irreversibly applies cached placement transforms to create scene objects; reversible via rollback but constitutes definitive data modification.
From the tool's definition Commit plan, apply transforms, create, rerolls, grid commits
Attacks that exploit this kind of access
The rule that runs commit_placement_plan 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 commit_placement_plan, this is the rule to start with:
commit_placement_plan 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 commit_placement_plan call is checked against it from then on.
Questions about commit_placement_plan
Commit a dry-run plan returned by place_along_path, grid_duplicate, or scatter_props. Plans are scene-scoped, capped, and expire after 10 minutes. Success consumes the plan; a complete rollback restores it for retry. The stored transforms are applied without rerolling randomness or repeating ground traces. Creation rolls back on failure; grid commits reject a changed/missing source before creating anything. Returns slot-to-GUID receipts. 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 commit_placement_plan: 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.
commit_placement_plan 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 commit_placement_plan 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 commit_placement_plan. 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.
commit_placement_plan 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