add_achievement_trigger
SCENE-MUTATING: generate a data-driven achievement trigger-zone component AND create its GameObject now (named zone with a sized BoxCollider, IsTrigger=true, at the given position). When an object tagged triggerTag enters, the component calls <achievementSetClass>.Instance.Progress(achievementId,...
This record as markdown: /tools/sbox/add-achievement-trigger.md
What add_achievement_trigger does on Sbox
AI agents call add_achievement_trigger 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 add_achievement_trigger is rated Critical
An AI agent that decides to call add_achievement_trigger doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Sbox is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs add_achievement_trigger 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_achievement_trigger, this is the rule to start with:
add_achievement_trigger 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 add_achievement_trigger call is checked against it from then on.
Questions about add_achievement_trigger
SCENE-MUTATING: generate a data-driven achievement trigger-zone component AND create its GameObject now (named zone with a sized BoxCollider, IsTrigger=true, at the given position). When an object tagged triggerTag enters, the component calls <achievementSetClass>.Instance.Progress(achievementId, amount) — or Unlock() when unlock=true — with a once-only latch and optional destroy-after-fire. Returns { created, path, className, achievementSetClass, achievementId, gameObject, attached, note, nextSteps }. The generated component only attaches to the zone after trigger_hotload — until then. 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 add_achievement_trigger: 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_achievement_trigger 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 add_achievement_trigger 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_achievement_trigger. 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_achievement_trigger 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